https://xitter.cf/t.co/6Q2PHk099s is a independent knowledge base and community hub for the Radix ecosystem.
Radix
Joined October 2022
- Tweets3.3K
- Following1.1K
- Followers1.4K
- Likes5.3K
Pinned Tweet
Thread of 🧵s:
Web3 City States:
xitter.cf/RadixWiki/status/16364…
Web3 is a network of city-states all fighting for liquidity.
Switching sides is costly, so the benefits need to be 10x to be worthwhile.
In a few weeks, #Radix will storm the citadels of Web3 with its arsenal of 10x Moments.
Here are our top ten: 👇🧵
A validator running hyperscale-rs, the community-built Rust implementation of a sharded Radix network, now checks the signatures on a certificate before it syncs toward the block that certificate names.
A certificate is a block's proof that a quorum of its shard's validators signed it. Validators pass them to each other, and one that sees a certificate for a height it does not hold syncs up to that height. Until this change it started the sync first and verified later. A forged certificate naming a height far above the chain could hold a validator in sync mode, proposing only empty blocks, until it restarted, because a sync has no exit for a height the network cannot serve.
Now a cited certificate is only a claim until its signatures check out. Each validator gets its own slots for claims, so one that floods forgeries fills only its own, and each refuted claim costs the checker a bounded number of signature checks before that sender waits a round to try again.
flightofthefox merged it on 19 Oct, with a test that sends that forgery: github.com/hyperscalers/hype…
Radix's entry for the CAIP namespaces registry had its first review on the spec yesterday, from Chain Agnostic, which runs the registry. CAIP is the naming scheme wallets and cross-chain tools share for a network, an account or a token.
The reviewer suggested shorter identifiers: drop the address prefix from accounts and tokens, since radix:mainnet in front of them already names the network.
x402, the HTTP standard that lets an AI agent pay for an API call inside the request, names networks the same way. @a_vaunt's x402 spec for Radix, filed in August, lets an agent pay without holding any radix:native: the agent signs only the payment, as a subintent, and the facilitator wraps the subintent in a transaction and pays the fee.
Both submissions: radix.wiki/developers/ai-age…
hyperscale-rs, the community-built Rust implementation of a sharded Radix network, splits a shard in two when it grows too large, and merges two when they shrink. A change its lead developer, flightofthefox, merged today decides what happens to transactions caught across a split or merge.
Until now a shard kept taking cross-shard transactions right up to the moment it split, and the ones caught mid-way were sorted out afterwards. Now the shard drains first: it stops admitting transactions to and from other shards, waits until every transaction it has already agreed to has its answer from the other shards, and only then splits. Transactions that touch that shard alone keep running throughout.
With nothing at fault, the drain takes at most 444 seconds, about 7½ minutes. If the splitting shard is waiting on a shard that has halted, and the drain misses its deadline, the split is cancelled rather than forced, so no transaction can commit on one shard and abort on the other.
The design, including what the pause costs: github.com/hyperscalers/hype…
The Radix Foundation has recovered 419k of the roughly 443k $USDC caught in an unfinished bridge transfer during the 31 August exploit, it said in the main Radix Telegram chat this morning. The bridge is Hyperlane, which links Radix to other chains.
The other 24.7k is stuck on Hyperlane's route to Solana. The Foundation spent three days on it with Hyperlane last week and is still working on it. Hyperlane advised against paying out the 419k while that recovery continues, so the Foundation is holding it.
The money is due back as hUSDC, Radix's bridged USDC, to the accounts that held hUSDC at the time of the exploit, in proportion to what each held. Governance proposal #3 settled that on 4 October with 95% of the vote.
radix.wiki/contents/history/…
A Scrypto developer can attach a fee to any function or method they publish. The Radix Engine, which runs every transaction, charges it on each call, so calling code cannot skip it, and the royalty owner receives all of it.
Other transaction costs are split: execution, finalisation and storage each go 25% to the validator proposing the round, 25% to the validator set and 50% to a burn. Royalties bypass that split.
There are two kinds. A package publisher sets developer royalties inside the blueprint, and calls to every component built from it pay them. A component owner sets owner royalties per method and can lock one for good, which gives anyone composing with that component a fixed cost.
Royalties are paid in radix:native, but an owner can set one as a USD amount, converted to XRD at a rate fixed for each protocol version.
radix.wiki/contents/tech/cor…
hyperscale-rs, the Rust implementation of a sharded Radix network, merged an experimental network layer on 17 October. It uses iroh, a library that connects two machines directly even when both sit behind home routers, and falls back to a relay when it cannot. A node now picks iroh or its existing libp2p layer at build time, and a new test bed seats a validator committee across different router types.
The rest of the week is in Issue #17 of the Week in Review:
radix.wiki/blog/week-in-revi…
On Radix, who may call a method is written once in the blueprint: one block maps each method to the roles allowed to call it. The engine checks the caller's badges against that rule before the method runs.
A Solana program has to confirm that every account it is handed is owned by the right program and signed by the right key. Anchor makes those checks when the developer picks the right type for each account.
radix.wiki/contents/tech/com…
Staking radix:native on Radix gives you a token back. Each validator has its own, called a liquid stake unit (LSU), and the validator mints it to you when you stake.
An LSU is a share of that validator's pool of staked XRD. Every epoch, about five minutes, the network mints new XRD for stakers and adds it to the pool, less the validator's fee. The number of LSUs you hold stays the same while the XRD each one redeems for goes up.
An LSU is an ordinary token, so it can be traded or deposited into another dApp while it keeps earning.
Getting the XRD back takes three steps: you return the LSUs to the validator, which burns them and gives you a claim NFT recording the amount and the epoch it unlocks; 2,016 epochs pass, about 7 days; then you hand in the claim NFT and receive the XRD.
radix.wiki/contents/tech/cor…
Radix Wiki | RadixWiki.xrd retweeted
Não vamos deixar Radix morrer, vamos engajar nossos soldados para que o projeto decole brevemente. Radix não é uma memecoin, mas sim uma das principais Layer 1 do mundo. Por mais que não estejamos bem, vamos fazer isso por Dan e por nós.
#radix
A Radix component that holds a token and gives it away takes 33 lines of code in the official hello-world example. The method that pays out is one line: take a token from the vault and return it. The caller's transaction decides where it goes.
Anchor's documented example of a similar job on Solana runs to 93 lines, most of them listing and checking the accounts it touches.
radix.wiki/contents/tech/com…
On Radix, one transaction can call several smart contracts, and either every step happens or none of it does.
On mainnet that is the normal case. Seböööl counted transactions on the Babylon ledger: 89.6% touch at least two components (Radix's smart contracts), not counting accounts. The median transaction writes 4 entries of ledger state; one in ten writes 19 or more.
A swap routed through two exchanges settles as one transaction. If any step fails, the whole thing reverts and only the network fee is charged.
How it works: radix.wiki/contents/tech/cor…
RadixDAO's first election now has a deadline. XRD holders ratified the DAO's rulebook on 2 October, which started a 90-day window: by 31 December the interim council must open the election for the Permanent RAC, the 5 to 7 elected members who make sure the DAO's proposals and votes follow its rules.
The ballot uses Majority Judgment. Each voter grades every candidate on five grades, from Excellent to Poor. A candidate's grade is the highest one that three-fifths of the voting power cast gave them or better; candidates are seated in order of that grade, and anyone whose grade falls below Good is not seated.
How the vote works: radix.wiki/ideas/dao-elect-p…
The Radix Guild's escrow contract has been run on Hyperscale-rs, the rewrite of the Radix node that splits the network into shards, in a simulated 4-shard network.
A member of the Hyperscale-rs Telegram ported the escrow to hyperscale-vm, the rewrite's smart-contract engine, where all 22 of its tests pass. On the simulated network every step is all-or-nothing across shards, including one transaction spanning 3 shards that is undone on all 3 when a later step fails.
Further runs cut the links between shards and dropped and replayed messages, and every transaction still completed in full or not at all. The runs found two bugs in hyperscale-rs; in one, a cross-shard transaction stays locked if shards stop exchanging certificates for about 20 minutes, with the funds held rather than lost. A fix is in progress, according to the project's Telegram.
radix.wiki/contents/tech/res…
Scrypto developers now have a free pre-audit kit: scrypto-audit-kit, open-sourced this week by bigdev, who also built the Radix Guild task marketplace. Scrypto is Radix's Rust SDK for smart contracts.
It reads a blueprint in two passes. The first is a fixed set of rules that needs no API key and flags patterns such as a component published with no owner, roles that can rotate themselves, floating-point maths and hardcoded addresses. The second, optional, has Claude work through an 11-class checklist: authorisation, reentrancy, decimals, resource handling, oracles, slippage and more.
Both feed one report that a person or an AI agent can read, and an MCP server lets coding agents run the audit, fix what it finds and check again. A report can also be turned into a Radix transaction that records it on ledger, tied to a hash of the exact source it read.
It is alpha, and the README says it does not replace a human audit: it is a cheap first read before paying for one. Install with pip install scrypto-audit-kit (Apache-2.0):
github.com/bigdevxrd/scrypto…
bigdev, the developer behind the Radix Guild task marketplace, has open-sourced DeFi Farmer, a yield advisor for Radix, under Apache-2.0.
It reads Ociswap, CaviarNine, DefiPlaza, Weft lending and native radix:native staking through the public Radix Gateway, and scores each option on risk-adjusted yield after impermanent loss, which is what a liquidity provider loses when the two tokens in a pool move apart in price.
When you pick one, it writes the transaction manifest, the plain-text list of steps a Radix transaction performs, and runs it through the Gateway's preview, which executes it against current ledger state without submitting it. If the dry run fails, the app never hands the manifest to your wallet. If it passes, you see what leaves your account and what arrives before you sign. The server holds no key and cannot move funds.
Feature work is paused until stablecoin liquidity returns to the venues it scans, and the code is maintained in the meantime.
github.com/radixguild/defi-f…
The same token payment works three different ways, depending on the chain.
On Ethereum, your token balance is a number in the token contract's storage. Sending tokens asks that contract to edit two entries in its own table.
On Bitcoin and Cardano, you hold unspent outputs from earlier transactions, and a payment has to name the ones it spends.
On Radix, each token you hold sits in a vault inside your own account, one vault per token. A payment says "withdraw 10 XRD from my account" and deposits them elsewhere. The transaction never needs to know where those tokens came from, and no token contract keeps the books.
radix.wiki/contents/tech/cor…
Flexathon was a solo hackathon Dan Hughes, the founder of Radix, ran over his holiday in late 2020 to demonstrate atomic composability across shards under Cerberus, Radix's sharded consensus design. A Radix Labs recording from May 2021 shows the demo. The page now also says that Xi'an, the network meant to run multiple shards, has no current launch date. radix.wiki/contents/history/…
Proven Network's domain has lapsed: it expired on 5 August and has sat in the registry's redemption period since 14 September. The page had said it was paid through 2027. Proven Network is the off-ledger compute project of flightofthefox, who now leads hyperscale-rs, and the two pages now link each other.
radix.wiki/ecosystem/proven-…
The Radix DAO's Conflict of Interest Policy and Code of Conduct were ratified on 2 October with the rest of its governance framework. The wiki's card now cites the ratified text in the DAO's own repository, and 21 other DAO cards point to it. radix.wiki/ideas/dao-coi-cod…
