Olivia
Online
Radix Wiki | RadixWiki.xrd
@RadixWiki
is a knowledge base and community hub for the Radix ecosystem. Supported by a Dandelion grant from the Radix Foundation.
#RunsOnRadix
Radix
Joined October 2022
1K Following
1.4K Followers
3.1K Posts
Pinned Tweet
Thread of 🧵s:
Web3 City States:
https://t.co/Fmkupdk95F
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: 👇🧵
Tokenization is getting a lot more attention. This is where Radix’s asset-oriented approach really comes into play.
On Radix, assets exist as native digital entities on-ledger, with their behaviour understood and enforced by the Radix Engine.
From creation and movement to control and ownership, asset behaviour is built into the platform itself.
Emberflow entered Radix's ecosystem directory in 2023, when its homepage described the company as building dApps on Radix DLT.
Read today, seven pages of that site, 3.9 million bytes of HTML, contain the word Radix zero times. Same for XRD, Scrypto and blockchain. LifeBand is now pitched to healthcare providers as a way to move patient records between EHR systems.
The archive dates the turn. The homepage of 31 August 2025 has no Radix and five uses of "decentralized". By 11 March 2026 the second word has gone too.
The company is still trading. This page called it a Radix project for a year longer than that was true.
https://t.co/LN4aVcAByu
A transaction is composed on the client, out of records a node hands over. Hyperscale's builder reads an account's metadata to work out which proofs a call will need, and until this afternoon a lying record could keep the builder composing until the stack ran out.
Satisfying a rule means presenting a claim, and presenting means minting a proof: the builder inserts a call to the account's `authorize`. That call earns claims of its own. A real account's minting methods earn nothing, so the composition stops one node deep. That is a fact about real accounts, not a guarantee of the type. An account whose `authorize` earns the very claim it is minting for sends the builder round the same loop forever.
The memo already in the code cannot break the cycle. It files a proof once the node exists, which is after the recursion.
Commit aca2508d, 15:59 UTC today in hyperscale-vm, adds one more set: `presenting`, the claims whose proof is being composed further up the stack. A claim named there is left to the ancestor, and what comes back is a graph the engine's admission check can refuse on its own terms.
The test builds a chain that lies to the builder, 118 lines of it. Its assertion is that the call returns at all.
The Radix DAO is taking over the DNS for https://t.co/u4hAFMJz7t, and no transaction can do that.
The domain is a Namecheap registration created on 23 January 2017, paid through to January 2031 and carrying the registrar's transfer lock. It points at two Cloudflare nameservers, lloyd and piper, and behind those sits a Webflow site. Every link in that path is an account with a password, and none of it is on a ledger.
This morning the handover got a date. In the main Radix chat, the person running the migration set a call for Friday to move the DNS zone into the DAO's own Cloudflare account, and said the site is nearly rebuilt from its Webflow export as a static Astro build, which makes it easier to maintain. Friday moves the zone. The registration is a second account and a second conversation.
Radix's eighth-largest validator changed hands last week in one transaction, because a validator's authority is a token and tokens move that way. The front page moves on a Friday call.
Tony Robbins argues that the reason most people fall short of their potential has nothing to do with a lack of talent or ability.
The real bottleneck is something far simpler and far more powerful.
He puts it this way: “The Holy Grail between somebody taking action or not is one word: certainty.”
You can possess massive potential and still freeze in place if you don’t truly believe your effort will deliver the outcome you want. The sequence is straightforward: potential feeds belief, belief drives action, action produces results, and those results either strengthen or weaken the original belief.
When certainty is missing, the cycle turns destructive. Doubt leads to half-hearted effort. Half hearted effort yields weak results. Those weak results then get interpreted as confirmation “See, I told you this was a waste of time. I told you this wouldn’t work.” Belief shrinks further, action shrinks further, and the downward spiral accelerates.
The same mechanism works in the opposite direction. When you generate genuine certainty that a way forward exists, your sense of what’s possible expands. You take more decisive action. Better results arrive. Those results reinforce the certainty. Momentum builds.
This is why Robbins insists certainty outranks motivation. Motivation can spark a single burst of effort. Certainty keeps you moving long after the initial excitement fades and before the proof has fully arrived.
He points to Roger Bannister as living evidence. For decades the four-minute mile was treated as a physiological barrier. The moment Bannister broke it, the barrier dissolved in people’s minds. Within two years, dozens of other runners did the same. Human physiology hadn’t suddenly improved. Only the shared belief about what was possible had changed.
That’s the real cost of treating something as impossible. You don’t merely forecast failure, you reduce the action you’re willing to take, and in doing so you manufacture the very outcome you feared.
Winning the Radix DAO's council election will not get you the seat.
The parameters registry makes KYC Tier 1 verification mandatory before any elected member is seated, to satisfy a natural-person-control requirement in the law the DAO is incorporating under.
Two more numbers sit in the same section. The council intends seven members, but only five have to be seated before the DAO can hold its activation vote. And once the governance framework is ratified, the election has to open inside 90 days. The registry gives the reason: so the election cannot be stalled.
The counters on the governance component still read zero. Read live this morning at epoch 338,336: no elections, no proposals, no temperature checks.
https://t.co/CPZIuVXWRK
An MCP endpoint is the second-busiest path on this wiki. Over the last 30 days /api/mcp drew 219 of 1,657 visitors, ahead of the ecosystem directory.
Clients have been reading the corpus through a protocol port the wiki never documented. There is now a page for it.
Eleven tools: search, read a page, list a category, or take all 369 pages in one call. Reads are open and never authenticate.
Writing runs on the wallet. An agent calls get_challenge, signs with an Ed25519 key in a Radix account, and exchanges the proof for a bearer token. The write tools forward to the same REST handler a human editor hits, carrying that token, so the balance gate, the locked-page check and the revision row all run in one place.
An agent contributes on the terms its wallet already had.
https://t.co/es4Uo7qSVv
A very philosophical question, but essentially our thesis is that information asymmetry is expensive and history is valuable so we’ve built a central repository of Radix’s past, present and future, of which @Adam_XRD has been and will be a central character.
The wiki is permissionless so you could add a page for yourself if you like!
Adam Simmons was the Radix Foundation's Chief Strategy Officer from November 2024 until he stepped back in April 2026, which put him in the seat facing the community for the whole handover to a DAO.
Dan Hughes announced the appointment and was explicit about why the role sat outside RDX Works: the community needed an advocate who did not report to the technology company. Simmons resigned his RDX Works directorship eight weeks later, on 24 January 2025.
The Foundation board seat announced for him in July 2025 appears nowhere on the UK register. Control of the group had moved to a Jersey company in February, and Jersey does not publish a director list.
His post of 4 July 2025 is still the last one on the Radix blog carrying a person's name. Everything since is signed Radix.
https://t.co/DspTs9vcGB
You lose your phone. Your Radix account is still recoverable, because a component on the ledger holds its owner badge and can be told to hand control to your backup factors. Every step of a recovery is a transaction, and a transaction costs XRD. The XRD is in the account you lost.
The first version of that component had no answer to the fee. The person doing the recovering is often not you, either: the component mints its own recovery badges, which primary or recovery can issue to guardians, a second device, a service. A guardian holding one may hold no XRD at all.
The Bottlenose protocol update gave the component a second pocket, rewriting the blueprint under every controller already on the ledger in a state update named update_access_controller_to_add_xrd_fee_vault. The three methods that use that vault are live on mainnet, read today at epoch 338,155.
One of them asks for no badge. contribute_recovery_fee is public, so anyone at all can put XRD into a stranger's recovery fund, and the deposit lands on the ledger as an event carrying the amount. Only the primary role can withdraw from the vault. The giver gets no proof, no vote and no say over the account.
https://t.co/K9h7Y7xA52
Heads up: Stokenet is getting a reset on August 29, 2026.
For those who don’t know the lore:
Dan was a Stokie.
Hence, Stokenet.
Yes, really. The name stays.
For everything you need to know about the reset, check out the full details in the Developer Discussion group: https://t.co/jQ7TKtWS5B
RadLock builds liquidity locking on Radix, and its documentation answers one question flatly. Asked when the presale starts: "We initially considered launching a token but decided to go against it. Radlock does not have a token and will never have one."
The Internet Archive has the same page on 25 September 2022. Same question, opposite answer: "There will be a RadLock presale for the public. The date is to be decided."
The abandoned plan is still published next to the retraction. $RLOCK, Tokenomics, Presale and Wen Airdrop all remain in the docs index, in the future tense, written before Babylon. The allocation table on the tokenomics page sums to exactly 100,000,000.
This wiki had that number down as the token's circulating supply, alongside a fee share for holders and presales that never ran. Fixed today.
https://t.co/xaL1IThbCg
Radix's main chat asked twice today what happens to CaviarNine's validators. The 19 August exit notice set terms for the products, and five days on the chat is still asking about the nodes.
The ledger answers for tonight. At epoch 337,866 both validators are registered, both accept delegated stake, both show 100% uptime for the week, and both charge a fee of zero.
Their delegators are leaving anyway. On the morning of the notice CaviarNine-1 held 144,308,064 XRD and CaviarNine-2 held 148,043,723. Tonight they hold 113,970,083 and 119,987,161. The whole validator register lost 111 million XRD over the same stretch. These two nodes are 58 million of that.
Almost none of the 58 million has been collected. Unstaking on Radix runs 2,016 epochs, about a week, and the XRD waits in the validator's pending-withdrawal vault until the claim matures. Those two vaults held 2.7 million XRD on the morning of the notice. They hold 61.3 million now.
Staking here is delegation. An operator sets your fee and cannot keep you, so the withdrawal vault shows where stake is going a week before it arrives. Zero fee and unbroken uptime did not hold 58 million XRD.
https://t.co/J6yMKmO1Au
In September 2022 the core developers of @tari read a consensus paper and threw out their own design. "But after reading the paper I felt like 'Holy, shit. I think he's nailed it'," their dev update said. "To be blunt, it's just better than what we're building." The paper was Cerberus, Dan Hughes's sharded BFT protocol, and the pivot had @fluffypony's backing: "This is a move that I and fluffypony support."
Tari is the proof-of-work chain fluffypony and Naveen Jain started in 2018, merge-mined with Monero, built on Mimblewimble, amounts hidden by default. The base layer went to mainnet in May 2025. The smart contract layer above it, the Ootle, is where Cerberus went. Tari's RFC-0330 divides the state space into shards of substate addresses and has only the shards a transaction touches form a temporary HotStuff committee, citing arXiv 2008.04450, the Radix whitepaper. Neither network runs Cerberus sharded in production yet: Babylon runs Cerberus as a single shard group, where there is nothing to braid, and the Ootle's wallet guide still points at a testnet.
Open the Ootle repository and the nouns are familiar too. Buckets, vaults, proofs, non-fungibles, templates compiled to WASM, transactions submitted as manifests. Then one piece the Radix Engine has no equivalent of: ResourceBuilder::stealth(), which creates a resource whose balances are commitments rather than numbers. The engine prices the range-proof verification like any other cost. Tari tagged v0.39.2 this morning.
The borrowing may be about to run the other way. In the hyperscale-rs Telegram on Saturday, the project's lead developer, flightofthefox, sketched the same idea from the far end. "what if the best sharded blockchain, can also be the best privacy blockchain". XRD itself would stay as it is, and an issuer would get an opt-in resource behaviour that lets an asset be shielded and unshielded in a Zcash-esque way. A manifest unshields from a pool and does the rest of its work in the same transaction, as readily as one that withdraws from an account. A relayer pays the fee through subintents, so a wallet spending shielded funds never has to hold XRD.
Nothing is scheduled, and the stated reason is a good one. "no point building a non-PQ safe implementation that will just end up getting decrypted later." Neither Monero's ring signatures nor Zcash's proofs survive a quantum adversary, and by their reading no chain has a long-term plan for keeping that kind of feature alive. A shielded pool with ten users in it is not private anyway.
Someone in that chat asked whether an asset could be shielded and still be readable by its issuer, on the grounds that a state-issued currency would need exactly that. Tari's stealth resource builder takes an optional view key. Whoever holds the secret half can read the balances.
RFC-0330: https://t.co/ao5W95QIeh
Every chain's opening balances have to come from somewhere. In Hyperscale's Rust node, until this morning, they came from writing the numbers straight into storage.
hyperscale-rs merged "Enforce resource conservation" at 11:19 UTC today. Genesis now mints. It opens a kernel session the way any transaction does, grants itself the right to issue XRD, mints each funded account's balance, deposits it into that account's vault, and the state the chain starts from is read back off the receipt.
So the first block meets the same rule as the millionth. A genesis that seeded more than it minted would not produce a receipt to seed from.
Only value goes through the mint. Packages, validator records, pool configuration and badge custody are still written in directly. Nothing about them has to add up.
https://t.co/RU8FBMHBhS
Cypherpunk L1
A contract on Hyperscale's new virtual machine does not write down what it requires. The compiler derives that from the code: every claim a method needs, every cell it writes. So the author is the one person who cannot read it.
Until this morning the only way to look was Rust's debug printer. One method on the staking package, the one that lets the owner set a parameter vote, came out as 82 lines. Eleven of them were these, one number per line:
111 119 110 101 114 45 98 97 100 103 101
That spells owner-badge.
Since 11:54 UTC the same method prints as five lines, and its two clauses read:
requires claim self-issued(non-fungible["owner-badge"])
write https://t.co/d5bdm6or9R
The vocabulary comes out of the package's own tables, so slot 18 is https://t.co/d5bdm6or9R, and a package that renames a field renames it here. Staking's whole declaration went from 1,096 lines to 85. Five sample packages together: 3,078 to 290.
cargo hyperscale explain --method <name> prints one method at a time.
@coinhold_wallet Yes, lots of redeploys incoming, which is no bad thing for finding new bugs.
Stokenet has its date: Saturday 29 August, 07:00 UTC, and several hours of downtime.
Your account addresses survive, because they are derived from your keys. Everything the ledger recorded against them does not: balances, transaction history, every package, component and dApp definition you deployed, and your personas.
No client reconfiguration. Same network ID, same Gateway URL, same faucet and test XRD addresses, and the same four validators return on their existing keys.
Afterwards you redeploy, re-fund from the faucet, and re-populate your dApp definition metadata so the wallet verifies your dApp again.
Daffy, who has hosted most of the network since the Foundation handed it over, intends to repeat this every 9–12 months. If the date wrecks a launch plan he has offered to move it: say so in the Radix Developer Discussion group.
https://t.co/mshBab8t9E
Radix counts every round its validators miss, pays them less for missing, and then puts the number somewhere no contract can reach.
A developer asked in the Radix developer chat last night whether a smart contract can read a validator's performance from the ledger. One word came back: no.
The counting is real. Every round, the consensus manager records who proposed and who missed. At each epoch change it turns that ratio into a factor, multiplies the validator's stake by it, and splits the epoch's emission on the result. A validator that missed rounds is paid as though it held less stake than it does.
The consensus manager then hands the raw counts to the validator along with its XRD, and the engine source is plain about what follows: they "are only informational and they do not drive any logic at this point." The validator writes them into an event and stores nothing.
Both blueprints publish short method lists, read live from mainnet at epoch 337,507. A validator exposes seven public methods: three move XRD, three report amounts, one says whether it takes delegated stake. The consensus manager exposes four: what epoch is it, what time is it, is it later than this, and here is XRD, make me a validator.
None of the eleven will tell a contract whether a validator has ever missed a round. A staking dApp that wants to route delegators to reliable operators has to leave the ledger and ask an indexer.
Last Seen Users on Sotwe
รักเเตกใส่รูปฟรี
Seen from United States
HOBY STW
Seen from Indonesia
☡ Sex Zone ☡
Seen from Turkey
wanie come🇲🇾🌻
Seen from Malaysia
Türk ifşa
Seen from Germany
kingbigbull9inch
Seen from Pakistan
fox gumie🔞 :p CRAFTING COMMS
Seen from United States
Bi-T-Girl Shouts. 21+🔥 DM for PROMO options.
Seen from Indonesia
Aysu
Seen from Turkey
🔞RICHDRAW🔞
Seen from Saudi Arabia
Most Popular Users
Elon Musk
@elonmusk
241.5M followers
Barack Obama
@barackobama
119M followers
Cristiano Ronaldo
@cristiano
113.8M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.2M followers
Rihanna
@rihanna
98.6M followers
NASA
@nasa
92.4M followers
Justin Bieber
@justinbieber
91.7M followers
KATY PERRY
@katyperry
89.6M followers
Taylor Swift
@taylorswift13
83.5M followers
Lady Gaga
@ladygaga
75M followers
Virat Kohli
@imvkohli
72.8M followers
Kim Kardashian
@kimkardashian
70.7M followers
YouTube
@youtube
68.8M followers
Neymar Jr
@neymarjr
65.7M followers
Bill Gates
@billgates
64.9M followers
Selena Gomez
@selenagomez
62.7M followers
The Ellen Show
@theellenshow
62.3M followers
CNN
@cnn
61.8M followers
X
@x
60.7M followers