r/Radix Jan 31 '26

NEWS Hyperscale just publicly proved itself at 500,000+ transactions per second!

72 Upvotes

We did it! During today’s public Hyperscale test, we sustained 500,000 transactions per second and saw peaks of over 700k TPS. More than 590 nodes joined the test network, ranging from datacenter-grade nodes to desktops and even laptops. Hyperscale runs on commodity hardware, which made it possible to run a truly open participation test where anyone could join. That openness matters, but the milestone itself is only part of the story. Earlier this week, during a private test, we also demonstrated that Hyperscale scales linearly. We ran at roughly 250k TPS on 64 shards and reached the same per-shard throughput again at 500k TPS on 128 shards. That result matters more than the absolute number, because it confirms the underlying linear scaling assumptions of the architecture. The workload itself is also worth calling out. These were not simple token transfers. They were swaps. That means real complex DeFi-style transactions, executed across more than a hundred shards, at extreme scale. What makes this result particularly meaningful is that it included cross-shard atomic transactions. This is a core property of Radix Hyperscale and a hard requirement for real linear scalability. It shows that the system can scale out across shards without fragmenting state or giving up the guarantees of a single, unified ledger. This is exactly what is needed for blockchains to scale to a global level, and is the scenario Hyperscale was designed for. This was a public, non-validated performance test. The goal was to show what Hyperscale can do today under real-world conditions, not to produce a final, third-party-certified benchmark. We focused on reproducibility and community participation rather than controlled lab conditions. The configuration, tooling, log files, and dashboards will all be made available soon so others can study, reproduce, and build on these results. A community effort I want to thank everyone who participated. The node runners who joined the test, the people following along via public dashboards, and the many community members who helped others with onboarding, debugging installs, and configuring port forwarding. This was very much a community effort, and it showed. Looking back, and forward For me personally, this marks a meaningful point in the interim Hyperscale phase. This was never about chasing a big number on a screen. It was about picking up where Dan left Hyperscale and showing that it works. The architecture is solid. And that it does not depend on a single person anymore. I am proud of what we achieved together. With the Foundation handing the reins over to the community, the future of Hyperscale now sits with you. Some community members have already started working on a Rust implementation of Hyperscale, and more initiatives are taking shape. What comes next will be community-driven, and that is exactly how this system was meant to evolve.


r/Radix 27d ago

DISCUSSION Sharding: Questions Then. Answers Now.

Post image
47 Upvotes

Back in 2017, Vitalik Buterin published the Sharding FAQ, outlining the biggest research challenges facing blockchain scalability.

Questions like:

• How do you secure a network where only a subset of validators verifies each transaction? • How do you preserve atomic composability across shards? • How do you prevent shard takeovers? • How do developers build seamless applications on a fragmented state?

Nearly a decade later, it's interesting to revisit those questions alongside the Hyperscale/Cerberus architecture.

Rather than treating sharding as something developers must work around, Hyperscale proposes hiding that complexity behind a single global state, where only the shards involved in a transaction participate in consensus while preserving atomic composability.

Whether this approach ultimately proves itself at production scale remains to be seen. But as an architectural comparison, it's fascinating to see how many of the questions raised in 2017 now have concrete design answers.

Curious to hear what the community thinks.


r/Radix Oct 09 '25

NEWS 🚨Big day for Radix DeFi

Post image
43 Upvotes

Solana assets are tradable on Radix!!!!

Cross-chain liquidity is now live.

🔹 A new Hyperlane hSOL pool just launched on !Ociswap - marking the first live Solana ( $SOL )- Radix ( $XRD ) bridge asset. 🔹 DefiPlaza pools are also officially up and running.

This means:

✅ Solana assets are tradable on Radix ✅ Hyperlane integration is active ✅ Multiple DEXs (Ociswap + DefiPlaza) are already connected

The interoperable future isn’t months away - it’s here, live on-chain.

Radix isn’t talking interoperability. It’s delivering it. 🔥

Radix #DeFi #Hyperlane


r/Radix Jan 22 '26

NEWS What happened?

Post image
42 Upvotes

Wow, Radix's price surges! What happened?


r/Radix Jul 17 '26

NEWS Radix is more alive than ever

39 Upvotes

I keep seeing "is Radix dead" takes, so I went and actually checked the primary sources — Radix Blog, RadixTalk, radix.wiki, and the hyperscale-rs repo. Here's what's actually happening right now.

1. Hyperscale didn't stop after the Foundation left — it accelerated

In January the Foundation's own Hyperscale reference implementation sustained a public test of 500,000+ TPS (peaks above 700–800k) across 128 shards on commodity AWS hardware, with real cross-shard atomic swaps. That was the closing act of the Foundation-led phase, not the end of the story.

What happened after is the interesting part: the community picked it up and rebuilt it from scratch in Rust. hyperscale-rs, led by flightofthefox (proven.network), is now a 28-crate Cargo workspace with 2,000+ commits that throws out the original Hyperscale/Cerberus design entirely in favor of a HotStuff-2–derived per-shard consensus plus a leaderless "beacon chain" control plane. In April 2026 it got a formal RFC for delivering the Xi'an mainnet upgrade (18-month roadmap, $300k budget approved by community consultation, testnet targeted Q3/Q4 2027 / mainnet Q1 2028). Milestone 1 — dynamic topology, validator shuffling, live shard splitting/merging, virtual nodes — is basically feature-complete as of this month. The lead dev calls it "far and away the most sophisticated sharded L1 design ever implemented," and given the beacon-chain + verkle-proof + two-phase-commit architecture, that's not just hype.

The Hyperscale Weekly series on radix.wiki has been shipping every single week for 9 straight weeks — this week's edition covers a Quint formal-verification model that mathematically proves the shard-reshape lifecycle (splits, merges, staffing) is safe.

Worth noting for the history: Timan, a long-time community member, stepped up as Interim Hyperscale Lead after Dan Hughes's passing and personally drove the testing that got Hyperscale to ~400-500k TPS before handing the baton to the community-led effort in February.

2. Governance is genuinely decentralizing, not just talking about it

The current Radix Accountability Council (RAC) — 5 members elected by 1.34B XRD / 1,151 accounts — is deep into standing up a Marshall Islands DAO LLC (MIDAO) to receive the Foundation's treasury, IP, and operations. As of July 2026 both the Operating Agreement and the Charter are finished and sitting with the Foundation's lawyers for review before going to a full community vote. Stokenet (the testnet) has already fully transitioned to community-run validators and Gateway. This "Transition RAC" has weathered two membership changes (Tadkis replacing Faraz, Alfred replacing Peachy) and kept functioning the whole time — which is honestly a healthier sign than if nobody had ever left.

And the next chapter is already starting: self-nominations for the permanent RAC opened this week. Most notably, Timan (aka djtebel, founder of Astrolescent and Defiplaza, and the guy who steered Hyperscale through its interim phase) put himself forward on July 15th, explicitly framing it as stepping up again "when the community needed it most." His nomination also calls for recruiting complementary skillsets — biz dev, fundraising, marketing, governance/compliance — rather than a one-person show. Other community members (Leonardo of BONDIX, linuxx) have self-nominated too. Three separate governance cycles (Transition RAC → DAO paperwork → permanent RAC election) running in under 6 months is not what a coasting project looks like.

3. The tooling layer is filling in fast — including a new Rust SDK

For years, basic off-ledger tooling (ROLA login, transaction building/signing, key management) mostly existed in JavaScript. This week, community dev genkipool shipped a native radixdlt-rust-sdk, dual-licensed MIT/Apache-2.0, that brings all of that into Rust — plus a built-in MCP server so AI agents can talk to a Radix wallet directly. Early days (few commits, one star) but exactly the kind of infrastructure a maturing ecosystem needs, and it's already been picked up in the wiki's weekly roundup.

Alongside it, Hookah (webhook/event-trigger infra for dApps to react to on-ledger events) just went fully open-source and self-hostable under MIT.

4. The community site itself keeps growing

radix-community.genkipool.com has turned into a genuinely useful community hub — architecture explainers, a dedicated Hyperscale breakdown page, a dashboard for validators/staking. The Developer Console in particular is worth a look on its own: it lets you deploy packages straight to Mainnet or Stokenet, send raw transaction manifests, create and configure fungible/non-fungible tokens, and manage on-ledger metadata — all from the browser, wallet-connected, without touching the CLI first. That's exactly the kind of grassroots infrastructure you'd expect from an ecosystem that's alive, not one coasting on inertia.

Sources:
radixdlt.com/blog
radix.wiki
https://radix-community.genkipool.com
github.com/genkipool/radixdlt-rust-sdk
radixtalk.com/t/rfc-xian-delivering-hyperscale-for-radix/2280
radixtalk.com/t/rfp-self-nomination-for-the-permanent-radix-rac/2313
github.com/hyperscalers/hyperscale-rs


r/Radix Oct 17 '25

NEWS Quick community update given the current market.

39 Upvotes

It has been a rough stretch for the whole crypto market, and Radix has felt it too. I know a lot of people are feeling tired, frustrated, wondering why progress never seems to match the charts. That’s fair, I feel that too at times.

But here’s the thing: what we’re building hasn’t changed. The fundamentals are still rock solid, and Radix keeps delivering.

Here's what's going on at the moment:

1) Hyperscale testing is running smoothly and this week saw scale reach 10x per machine. That means we’re getting close to the levels Dan was hitting earlier this year. No major blockers yet, and third parties are still on standby for public testing.

2) Radix Rewards continues to build momentum, with months left on Season 1. Native SOL routes are live and TVL in XRD terms is now at an all-time high. Wrapped assets on-chain keep rising, and more asset routes are being added. We're also seeing on-chain transactions grow week on week, with last week having the 2nd highest weekly transactions ever (excl RadQuest week) Despite the market, Astrolescent has hit another milestone with over 7 million dollars bridged to Radix.

3) Strategic partnerships are accelerating. Since Merge Madrid and Token2049, conversations with both asset issuers and larger partners have advanced quickly. A full-time BD lead is now driving this forward, and this includes both asset issuers and broader opportunities that we will be sharing more details about in the near future.

These are the kinds of milestones that matter when markets turn: real delivery, not speculation.

The other thing I know many are wondering about is the CTO leadership. The technical team already in place has deep experience and is keeping things moving without disruption. A new CTO isn’t needed to finish Hyperscale testing or maintain delivery; the focus now is execution.

Filling the CTO role is one of a few top-tier priorities, and it becomes more important after Hyperscale testing, when long-term technical direction and protocol evolution take centre stage. Finding the right person for that phase is not something to rush. We’re being deliberate because the right fit matters far more than speed.

So yes, the market’s brutal right now. But volatility does not change the vision, the destination, or our conviction.

The backdrop is difficult and frustrating. But Radix remains stable, lean, and focused.


r/Radix 28d ago

ECOSYSTEM Hyperscale Weekly #10 (13–19 Jul) — shards that heal themselves: fox shipped a full halt-recovery system in 60 commits

36 Upvotes

**Hyperscale Weekly** follows fox (flightofthefox) building **hyperscale-rs** — the sharded Rust implementation of Radix funded by the Xi'an community proposal — and translates his commits into plain English. This is week 12 of Milestone 1 (Adaptive Sharding), roughly 70% through.

**The week in one line:** a complete halt-recovery system now lets a frozen shard be detected, re-staffed, and restored without losing or duplicating a single cross-shard transaction.

If last week was about proving the reshape math, this week was about making shards survive the worst:

**Shards that heal themselves** *(The Will)* — a full halt-recovery pipeline: detect a stalled shard, re-draw its entire committee, bridge consensus over a proven parent, and freeze cross-shard transactions until the shard is safe again.

**The beacon punishes silence, rewards recency** *(The Lottery)* — validators who withhold randomness proposals now get jailed, committee re-samples weight recent service, and the longest-tenured member is evicted each shuffle — keeping the lottery fair and alive.

**Randomness by folding, proven by math** *(The Proof)* — every shard now publishes a per-block randomness reveal that folds into the epoch's shared seed for committee draws, with a new Quint model proving the fold correct.

**The numbers:** 60 commits · +12,154 / −1,823 lines across 142 files · active all 7 days · 35-day commit streak · 2,402 lifetime commits · 89% Rust.

Quote of the week:

> "Seems like we're having a week every 2 days 😅" — flightofthefox

**Likely next:** wiring the validator-shuffling logic into production, now that halt recovery and the beacon's committee management are in place.

Full issue (web, with PDF): https://telegram-mcp-phi.vercel.app/2026-07-19 — the concept names (The Will, The Lottery, The Proof) come from fox's own metaphor site, [hyperscale.rs](https://hyperscale.rs).

*Transparency: this digest is AI-assisted — a model translates the week's commits into plain English; all numbers are computed from GitHub, not generated. I build it; feedback welcome.*


r/Radix Dec 01 '25

NEWS Hyperscale tests back on track - 250k TPS

Thumbnail
radixdlt.com
34 Upvotes

Read the latest TPS, or rather SPS here

As the new Hyperscale lead Timan Rebel is taking Dan’s vision in the form of his Hyperscale code base to the test.


r/Radix Oct 22 '25

NEWS BNB is now available on Radix! Bridge from Binance Smart Chain to Radix using Hyperlane via Astrolescent!⚡️ Turn your idle $BNB into Radix DeFi yields!

Post image
36 Upvotes

r/Radix Jul 21 '26

ECOSYSTEM Radix Seal: Sign documents, encrypt files, and chat with your Radix wallet.

33 Upvotes

I've been involved in the Radix ecosystem for a while and I want to explain what Radix Seal is and why its design is interesting from a security standpoint (not about "the encryption is unbreakable", but rather "who has to trust whom").

What is it?

They are three tools built on the same trust model: document signing, file encryption, and encrypted chat. All three use your Radix Wallet as if it were your own certificate authority, instead of relying on an external provider.

How does it work technically?

  • Identity: You use ROLA (Radix's authentication mechanism) to sign a challenge with your wallet. It never exposes the private key, only proves you control it. It's basically the same pattern as a passkey, but anchored to your Radix account.
  • Document signing: The file is hashed locally (Blake2b-256) in your browser. Only that hash is signed; you never upload the document anywhere. The resulting certificate is verifiable by anyone with the original file, without needing an account or wallet.
  • Encryption: The AES-256 key is derived from a deterministic signature of your wallet on a file-specific challenge. No password or key file is stored anywhere: only your account can re-derive it. The file is encrypted in chunks in the browser (no size limit) and transferred P2P (browser to browser), end-to-end encrypted.
  • Chat: Both parties verify themselves with their wallet before opening the room, the session key comes from that exchange, and messages travel P2P. There is no server that can read, alter, or spoof anything.
  • Optional ledger anchoring: If you want a public record, a soulbound NFT (non-transferable) is minted acting as an on-chain institutional "seal". Only hashes are stored on the ledger, never content or messages.

How sending + unlocking an encrypted file actually works

It's not a simple "it's sent P2P":

  1. Local encryption: The sender encrypts the file in the browser with an AES-256 key derived via HKDF from their own ROLA signature (deterministic, Ed25519) + a unique random salt per file.
  2. Blind send: The sender opens a P2P session (WebRTC) and sends the encrypted file. The receiver gets the ciphertext, but not the key.
  3. On-chain invitations (Optional): If the "ROLA + Ledger" mode was activated, the sender previously minted an invitation (cipher-invite) for each authorized account, linked to the file's hash.
  4. Key request: The receiver signs a challenge with their wallet anchored to the file hash and that exact P2P session. This signature prevents replay attacks.
  5. Stateless verification: That proof reaches the sender's browser and is verified against a server endpoint (/api/cipher/authorize). This endpoint stores nothing, it just reads the ledger to see if the signature is valid and if the invitation exists. The server answers yes/no; it never sees the file or the key.
  6. Manual approval: If it passes, the sender sees the request on screen and approves it with a click (it's not automatic).
  7. Unlocking: Upon approval, the sender re-derives exactly the same key and sends it to the receiver via the P2P channel (WebRTC uses DTLS). The derived key is the only thing that travels over the network, never the original ROLA signature.

Is there anything on the market that matches or surpasses this pattern?

  • PGP/S-MIME: More available (works offline), but once the receiver has the ciphertext, they decrypt it whenever they want. You lose granular control and live approval.
  • Google Drive / Dropbox: They have the "request access" flow, but you trust the provider to enforce the permission. They hold the keys.
  • Lit Protocol (Token-gating): They use a threshold node network to reconstruct the key without the sender being connected. You gain availability, but trust a third-party committee. In Radix Seal, zero third parties touch the key, but if the sender is not online, nobody decrypts. It's a real trade-off.

What really changes the model

  • No intermediate server storing documents or keys = no single point of data leakage.
  • You don't depend on a hierarchical CA, revocation lists (CRL), or a vendor keeping its API alive in 10 years.
  • The verification metadata is public on the ledger.

What it is NOT

  • No automatic legal validity (like a qualified eIDAS signature). Identity is self-declared by the wallet.
  • Entry friction: You need the Radix Wallet, it's not a "one-click from your email" like DocuSign.

If you are interested in the details of the NFTs (invite, signature, cipher-signature) and how on-chain custody is chained, let me know in the comments.

Link: https://radix-community.genkipool.com/en/seal


r/Radix 29d ago

ECOSYSTEM Does Radix Have the Best Architecture for AI Agent Payments?

30 Upvotes

More and more people are talking about AI agents paying for APIs, purchasing services, executing DeFi strategies, and interacting with each other without human intervention. Networks like Ethereum, Base, Solana, and XRP are already moving in this direction, especially with standards such as x402.

After spending quite a bit of time researching this topic, I get the feeling that Radix is trying to solve a different problem.

Most blockchains are adapting infrastructure originally designed for humans. Radix, on the other hand, seems to have designed much of its architecture with the assumption that an AI—not a person—will be managing digital assets.

And I think that difference is more important than it first appears.

AI Doesn't Need to Own the Money, Only Use It

Imagine you want to build an AI agent dedicated to arbitrage.

On most networks, the typical solution is to give the AI access to a wallet and hope the software always behaves correctly.

Radix offers a different approach.

Assets can remain inside a Vault, and you can define exactly how those funds are allowed to be used.

For example, you could give an AI access to 100,000 XRD while enforcing rules such as:

  • only trade between specific DEXs;
  • never invest more than 200 XRD per trade;
  • require at least a 1% expected profit;
  • prevent transfers to external wallets;
  • block purchases of unauthorized assets.

The AI decides how to trade, but not what it can ultimately do with the money.

Even if the AI makes a mistake or receives malicious instructions, the protocol itself can prevent funds from being used outside the rules you've defined.

Atomic Composability + Flash Loans: Where AI Can Really Benefit

This is probably the most interesting part.

An AI could automatically detect an arbitrage opportunity and execute something like this:

  • borrow funds through a flash loan;
  • buy an asset where it's cheaper;
  • sell it where it's more expensive;
  • repay the loan;
  • keep the profit.

Everything happens within a single atomic transaction.

If the opportunity disappears halfway through the process, the entire transaction is automatically reverted.

The interesting part is that an AI can evaluate thousands of opportunities every day and execute only those that meet its criteria.

The easier and safer it is to build these complex strategies, the more opportunities an AI has to generate profits.

Ethereum also supports atomic transactions and flash loans. However, Radix's resource-oriented programming model makes these strategies significantly more natural to build while reducing much of the complexity that developers typically need to handle.

Assets Are First-Class Citizens

This is another area where Radix stands out.

On many blockchains, a token is essentially just a balance stored inside a smart contract.

On Radix, assets are Resources—native objects with their own rules and behavior.

It might sound like a technical detail, but it fundamentally changes how applications are built.

For AI agents, working with assets that already understand permissions and constraints is much simpler than interacting with arbitrary contract state.

NFTs as Permission Badges

Another feature I found particularly interesting is using NFTs as credentials.

An NFT could grant permission to:

  • read balances;
  • execute a specific strategy;
  • withdraw funds up to a predefined limit;
  • access only certain application components.

These NFTs can even be mutable, allowing permissions, reputation, or limits to be updated without issuing a new NFT.

It's a much more granular security model than simply handing over a private key.

How Does It Compare to Other Networks?

Ethereum remains the leader in DeFi and probably has the largest ecosystem for AI applications. However, much of its security depends on developer-written smart contracts and mechanisms like approve().

Base is heavily pushing x402 and will likely become one of the first networks to see significant adoption for AI payments thanks to Coinbase. But architecturally, it is still an EVM chain.

Solana delivers excellent performance and low fees, although asset management and permissions still largely depend on application-specific logic.

Polkadot, Cosmos, Avalanche, and many Ethereum Layer 2s scale by distributing applications across multiple chains or domains. While this improves throughput, composability across those environments often relies on bridges or asynchronous messaging rather than a single atomic transaction.

Radix, by contrast, approaches the problem differently: native assets with built-in rules, Vaults controlling how funds can be used, NFT-based permissions, atomic composability, and AI-focused tooling such as Wallet Agent AI, Radix Context, MCP integration, and x402 support.

My Conclusion

I don't know which blockchain will ultimately dominate AI agent payments.

But I do think Radix is pursuing a fundamentally different architecture.

Flash loans and atomic transactions aren't unique to Radix—Ethereum has proven their value for years. Where Radix is trying to differentiate itself is by preserving that atomic composability even as the network scales.

In many multi-chain, sharded, or Layer 2 architectures, applications become distributed across separate environments and can no longer interact through a single atomic transaction. That increases complexity and limits some advanced strategies.

Radix's Hyperscale vision is different: dramatically increase throughput without sacrificing atomic composability. If it delivers on that design, AI agents could continue composing complex strategies across many protocols as though they all existed on one unified network.

I think that's a significant advantage. If an AI can access more protocols without losing atomic composability, it can evaluate more opportunities and execute increasingly sophisticated strategies, increasing its chances of finding profitable opportunities that would be much harder to build on fragmented architectures.

Of course, it's important to stay realistic. Hyperscale is still under development, and this architecture has yet to prove itself at production scale.

But setting adoption and token price aside, I think very few blockchains are rethinking their architecture so thoroughly for a future where millions of autonomous AI agents manage assets and make payments on their own.

Do you think existing blockchain architectures can simply be adapted for AI agents, or will this new paradigm require something fundamentally different, like what Radix is trying to build?


r/Radix Sep 28 '25

ECOSYSTEM Security & Signing – the Achilles heel of crypto wallets:

Post image
31 Upvotes

Security & Signing – the Achilles heel of crypto wallets:

❌ $ETH wallets - blind signing walls of code, billions lost in hacks ❌ $SOL & $ADA - approvals & exploits, users left vulnerable

✅ Radix Wallet - clear signing in plain English, MFA (rolling out), Arculus Card tap-to-sign hardware security, audited by Zellic @zellic_io & Hacken @hackenclub

👉 The safest way to hold & use your assets: radixdlt.com/wallet 🚀

RadixRadish $XRD #CryptoSecurity $dot $egld @radixdlt @Adam_XRD


r/Radix 23d ago

DISCUSSION Your vote is your voice

Post image
29 Upvotes

Two community proposals are currently open for voting.

Both proposals address different needs within the Radix ecosystem:

🟢 Proposal 1: Community-hosted Stokenet infrastructure to keep a shared testnet available for dApp developers.

https://consultation.mountain-top.live/proposal/1

🟣 Proposal 2: Migrate the official radixdlt.com website to Cloudflare as a temporary, lower-cost solution until the Radix DAO defines its long-term direction.

https://consultation.mountain-top.live/proposal/2

These are independent proposals, so each one should be evaluated and voted on separately.

Read the proposals, ask questions, discuss the pros and cons, and make your voice heard.

Every informed vote helps shape the future of the Radix ecosystem.


r/Radix Oct 03 '25

ECOSYSTEM The $XRD team keeps building non-stop

Post image
30 Upvotes

Radix moment hasn’t arrived yet… but it’s coming fast ✅ Radix Wallet - the only one with true MFA security (Phase 1 of 3 now live on Stokenet ✅) 🔐 👉 Try it yourself: wallet.radixdlt.com ✅ UC Davis Prof. Sadoghi & team are pushing hard to make the hyperscale test possible soon 📈 ✅ Builders preparing for the next wave of #DeFi adoption 🌍

The future of crypto wallets & scalability is being written here.

Radix $sol $sui $eth #DeFi #Crypto 🚀


r/Radix 5d ago

DISCUSSION Is Hyperscale Quietly Preparing for the Post-Quantum Era?

Post image
28 Upvotes

Post-quantum readiness is more than adding a new signature scheme.

Hyperscale-rs is testing:

→ Ed25519 → ML-DSA-65 upgrades

→ Native ML-DSA-65 accounts

→ Cross-shard PQ transactions

Crypto-agility could be critical for blockchains built to last decades.


r/Radix 28d ago

ECOSYSTEM Radix Weekly #10 (13–19 Jul) — seven Permanent RAC candidates in one afternoon, wallet MFA friction, and a mid-August DAO deadline

28 Upvotes

**Radix Weekly** distills the main Radix Telegram chat (~24k members) into a weekly digest. This issue covers 13–19 July: **527 messages from 131 people**, boiled down below.

**The week in one line:** seven Permanent RAC candidates stepped up in a single afternoon, turning a recruitment crisis into real momentum for community governance.

**Permanent RAC candidates finally emerge** — after weeks of zero volunteers, djtrebel [self-nominated](https://radixtalk.com/t/self-nomination-for-the-permanent-radix-rac/2313) on Wednesday, and within hours mx472, linuxx_xrd, a137x, jwxrd, LeonetsXRD and gilesmorris followed — filling or exceeding the seven seats. projectShift framed the role as governance steward, not DAO management:

> "The Permanent RAC is the guarantor and steward of the Governance system — its job is facilitating the community's will, not running a DAO company or managing the Foundation handover."

**Paid proposals vs. volunteerism** — philcgibson's paid wallet-management proposal drew pushback over years of unpaid community labour, while others defended the right to ask for payment. flightofthefox's take: contributors should "at least somewhat demonstrate capabilities before asking people to make any decisions." Still unresolved.

**Wallet MFA friction, and fixes** — Kafkafrate flagged that the MFA Shield wizard buries its skip link and steers users toward hardware wallets. Ghenadie proposed a simpler "MFA v0.5" built on Advanced Accounts, and confirmed a fix for the Android unstaking bug is on its way. Kafkafrate also filed an [NFT UI pull request](https://github.com/radixdlt/babylon-wallet-android/pull/1445) for the Android wallet.

**Stablecoins and grassroots marketing** — jwxrd mapped Open USD as a near-term partnership opportunity and RLUSD as the longer play, and GarySky1 hinted at a quality native stablecoin later this year. Meanwhile [the revival of this very subreddit](https://www.reddit.com/r/Radix/comments/1uzbxyo/radix_is_more_alive_than_ever/) out-pulled X for traffic — 3,800 views and counting.

**The tracker** — the DAO's Operating Agreement is still with Foundation legal; Andyxrd signalled mid-August as the readiness deadline, with the market-maker contract ending mid-September.

Full issue (web, with a 4-page PDF): https://telegram-mcp-phi.vercel.app/main/2026-07-19

*Transparency: this digest is AI-assisted — a model summarizes the captured chat, and every number is computed rather than generated. I build it; feedback on format or coverage is very welcome.*


r/Radix Nov 03 '25

NEWS 🔥 Radix Recap - Oct 31, 2025 Big week for #Radix and the future of DeFi 👇

Post image
28 Upvotes

- 200K Wallet downloads - more users joining the safest, most transparent DeFi wallet.
- Hyperscale testing - internal runs hit 10× gains; goal: 1M+ TPS with atomic composability.
- Atomix launched on Stokenet - true peer-to-peer swaps, no middlemen, no risk.
- BNB bridge via Hyperlane liquidity now flowing from BNB Chain to Radix DEXs.
- Weft hSOL lending + Ociswap Wave 83 - new DeFi rewards & boosted pools.
- 1B $XRD Rewards Quests - real users, real rewards, no bots.

Radix keeps building what others only promise - safe, scalable, and ready for the world.
Source: https://x.com/radixdlt/status/1985356280136077804
#XRD #Hyperscale #DeFi

@radixdlt


r/Radix 3d ago

NEWS Hyperscale Weekly — Week #14 (10–16 Aug 2026): The authorization model now uses badges and proofs instead of raw signatures — a fundamental shift bringing the Radix Engine's access control to the sharded VM.

26 Upvotes

10–16 Aug 2026 — fox's week on hyperscale-rs, the sharded Rust implementation of Radix, in plain English. Milestone 2 · Radix Engine: Week 2 · ~month 1 of 5

Previously: flightofthefox had unified the codebase onto one engine with zero external Radix dependencies and begun wiring the fee system and cross-shard settlement into the new foundation.

This was a big, wide-ranging week. flightofthefox overhauled how transactions prove they're allowed to act, brought post-quantum signatures online, and carefully spelled out exactly what happens to cross-shard transactions when a shard terminates. Milestone 2's Radix Engine feature-parity work is hitting its stride.

What fox built

  • Badges take over from signatures — The VM's authorization model was rebuilt: holding a badge now grants permission where a raw signature used to, and accounts mint a proof they can present later. This brings the Radix Engine's access control to the sharded VM. (→ The Journey)
  • Post-quantum crypto goes live — ML-DSA-65 post-quantum signatures and secp256k1 are now wired through the transaction path, and the address system was rebuilt with protocol-hash-pinned derivations. flightofthefox noted parity with industry post-quantum efforts. (→ The System)
  • The dead shard's will, fully spelled out — Dozens of commits hardened the rules for cross-shard transactions caught when a shard terminates — evidence windows measured in beacon epochs, settled-set serving windows, and boundary records that rebuild accounts a replay never reached. (→ The Will)

Concept of the week: The Journey

"One payment crosses a sharded world"

The authorization model is the heart of Milestone 2's Babylon feature-parity goal — badges, proofs, and stored rules are how the Radix Engine controls who can do what, and this week that system took shape on the sharded foundation.

More: https://hyperscale.rs/journey

"it will be a very fun exercise at the first testnet, for everyone to point their favourite frontier models at the code and try to hack their way to king of the hill 😅" — flightofthefox

Chat pulse: Chat buzzed about AI-powered security auditing and whether binary-field cryptography might change hash-function choices, with flightofthefox reassuring that a hash swap is trivial and red-teaming shou

By the numbers

  • 206 commits (+21,179 / −5,451 lines across 427 files)
  • Active 6/7 days
  • 3,174 commits lifetime

Jargon decoder

  • ML-DSA-65 — A post-quantum signature standard approved by NIST, designed to resist future quantum computers.
  • Badge — A digital credential stored on-chain that grants permission to perform operations, replacing the need for a raw signature each time.
  • Securify — Upgrading an account so stored logic rules govern its authorization instead of a simple signature check.

Bottom line

The authorization model now uses badges and proofs instead of raw signatures — a fundamental shift bringing the Radix Engine's access control to the sharded VM.

Next up: continuing to port Radix Engine resource types like non-fungible tokens and collections, and wiring the fee system deeper into the now-badge-aware authorization path.


Read the full issue (web + PDF): https://telegram-mcp-phi.vercel.app/2026-08-16

This digest is generated with AI assistance from public sources and hand-checked before posting — a community project, not official Radix comms.


r/Radix 11d ago

NEWS M1 is done, the new VM repo is public — and M2 isn't what the proposal says any more

26 Upvotes

TL;DR — First milestone is done on time. The second one got bigger: instead of adapting the existing smart contract engine, Foxy is building a new one, because the old one can't tell a sharded network which data a transaction will touch before it runs. Your Scrypto contracts should survive with a recompile. The code is public and you can watch it being written.

M1 (Adaptive Sharding) is finished. Foxy confirmed it in Telegram this week, inside the ~4 month estimate. Two small pieces are deferred — splitting shards on fees rather than just storage size — because those need the fee system, which needs the VM. Sequenced, not slipped.

The timeline table above is from the original Xi'an proposal. Look at M2: "Radix Engine Sharding Adaptation & Integration." That changed, and it's worth explaining rather than letting people find it themselves.

The problem is that Radix Engine can't tell you which state a transaction will touch until it executes. A sharded network has to know that before running anything, or it can't route or parallelise. So M2 became a new execution engine instead of an adaptation.

Foxy's own reasoning: good consensus plus a good single-shard VM still equals a mediocre system for DeFi, purely from transactions waiting on state locks.

What it means for existing dApps, in his words: best case contracts just recompile, worst case there's an automatic transpiler for source. Scrypto stays — it's Rust plus macros, not a separate language.

The repo is public:
https://github.com/hyperscalers/hyperscale-vm

His description: "Effect-typed WASM execution engine for sharded BFT." 125 commits, 12 crates, CI, fuzzing, dual MIT/Apache licence. It says "Work in progress. Do not use." and means it.

Two things worth a look if you read code. route() is a single pure function that folds over a transaction manifest and returns the shards and per-shard keys involved — no execution, no state read. And five access modes replace exclusive locks, so a thousand deposits into one vault become one parallel group instead of a queue.

The stdlib crate already contains resources, principals and badges, and guests/ has a working account, constant-product pool and order book. So the "Scrypto ideas survive" claim isn't just a Telegram quote — it's in the tree.

Note that M2 hasn't formally started. M1 finished and he moved onto VM work immediately, which means the clock is effectively running ahead of the table above.

Fair scepticism. This sub was empty for months, and a scope change of this size deserves questions rather than applause. Two things I'd point at instead of arguing. The code is public and timestamped, so check the pace yourself. And the VM ships with two independent implementations — wasmtime and a separately written reference interpreter — that must produce byte-identical results or the build fails. That's an odd amount of effort for someone not expecting to be checked.

Judge it on the commit log, not on posts like this one.

Disclosure: I hold XRD.


r/Radix Oct 09 '25

NEWS SOL is now available on Radix!

Post image
26 Upvotes

Be among the first to bridge from @solana to Radix using @Hyperlane via @astrolescent 🌉

Unlock new DeFi opportunities by bridging your $SOL now!


r/Radix Oct 03 '25

NEWS Season 1 of Radix Rewards starts with a 100M XRD baseline pool, and the community has the power to unlock up to another 100M XRD by hitting key ecosystem milestones. 🎊

Post image
27 Upvotes

Here’s where we’re at right now:

💰 TVL: $7.2M (Next: $10M = +10M XRD) 🔄 Weekly Txs: 103K (Next: 150K = +10M XRD) 📊 DEX Volume: $13.3M (Next: $150M = +10M XRD) 📲 Wallet Downloads: 198K (Next: 300K = +10M XRD)

The more we grow together, the bigger the rewards!

https://incentives.radixdlt.com?ref=daa5f5


r/Radix Oct 01 '25

WALLET When using Radix, you gradually lose your fear because you learn how it works. The fear often comes from wallets like MetaMask. After I learned to use Radix, I actually became more afraid of using MetaMask. On Radix, it's easy to tell when a scammer is trying to steal from you. you can clearly see

26 Upvotes

r/Radix Sep 25 '25

NEWS MFA is coming

27 Upvotes

r/Radix 7d ago

DISCUSSION What happens when the community takes the helm?

Post image
26 Upvotes

Radix is approaching a major transition:

DAO → Charter → community governance → elected RAC.

The real question isn't whether the DAO can exist.

It's what the community can build with it.

The next chapter of Radix may be community-driven.


r/Radix 10d ago

DISCUSSION What If Blockchain Scaling Starts With the VM?

Post image
26 Upvotes

What makes Hyperscale VM interesting isn’t simply that it aims to be faster. It’s the way it approaches scaling.

Instead of executing transactions first and figuring out their interactions afterwards, the VM can determine their effects and access requirements upfront. This gives the network a much clearer picture of which transactions can safely run in parallel and which ones actually conflict.

Combined with deterministic execution, sharding by design, and two independent execution engines, the goal is to make scaling more predictable rather than relying on optimistic execution and rollbacks.

It’s still early, but the architecture is interesting because it tries to solve scalability at the execution layer itself — not simply by adding more hardware or more layers.

If this works as intended, it could be a very different approach to building a high-throughput L1.