Great work by the @RippleXDev team on a fast, well-coordinated response to the critical Payment Engine vulnerability. In collaboration with RippleX and @XRPLF, we are formally verifying critical parts of the XRP Ledger in order to identify deeper issues that conventional testing may miss, and to bring stronger formal guarantees to the protocol.

The recent XRP Ledger security fix raised a lot of questions and some misconceptions. Let's clear them up. 1. Was any XRP created? No. XRP's supply was fixed at 100 billion when the XRP Ledger launched, and no transaction is allowed to create more. This bug was a way around that rule, and 3.4.1 fixed it 2 weeks ago. You don't need to trust us on this. All ledger data is public, and explorers and data sites read it every day. New XRP would show up in account balances for everyone to see. There is no hidden place for XRP on the XRP Ledger, every balance is public. We monitor the XRP Ledger 24/7 and have verified the supply throughout the history of the ledger. Others in the community verified this too, and anyone can do the same. Transaction fees are destroyed, so the supply is deflationary. About 99.986 billion XRP exist today. 2. How did this go unnoticed, and what's next? No normal payment comes anywhere near triggering it. It took hundreds of deliberately constructed operations. AI makes bugs like this faster to find, for the bad guys and the good guys. Together with RippleX and the community, we will ensure the XRP Ledger is protected against such vulnerabilities. This means radically applying Formal Verification and AI adversarial testing, collaborating closely with security researchers, and strengthening the bug bounty program. You'll hear a lot more about this as we progress. 3. XRP Ledger decentralization at the core of this. A public fix shows attackers where the bug is, and AI makes that fast. With a normal amendment vote, the fix would have been public for weeks before it took effect, risking network security. As a reaction to this, the XRPL community came together, and among them the XRP Ledger Foundation, RippleX, core devs and validators formed a social consensus and agreed on a path forward that involves shipping the fix directly. Patching a live network is never trivial, so the plan was also designed to minimize disruption for everyone running on it. We shared the build with the default UNL validators, using the contact details each one publishes in its xrp-ledger.toml file. Public binaries followed the same day, September 25. No single party could make that call alone. Every validator and node operator chooses what software to run, and 3.4.1 only became required through a normal amendment vote with more than 80% validator support for two weeks. Protocol changes still go through amendments. Big thanks to Cayden Liao and Veria AI for finding and reporting this responsibly, to the XRPL core developers for building and testing the fix, and to every node operator who upgraded so quickly, especially the validators. Full report:

Security remains our top priority for preserving trust in the XRP Ledger (XRPL). Sharing a few thoughts following yesterday's disclosure of the critical payments engine vulnerability reported by Veria AI. First, this was a serious vulnerability, and we don't take that lightly. The bug had existed in the codebase for over a decade and could have allowed XRP to be created beyond its fixed supply. Fortunately, it was discovered through our bug bounty program before it could ever be exploited. Second, our response was fast and coordinated. The team developed and thoroughly tested a fix, worked closely with validators to rapidly upgrade the network, and secured the ledger before public disclosure. I'm proud of how everyone came together to address the vulnerability and protect the XRPL network. But there's a much bigger lesson here. AI is fundamentally changing how quickly vulnerabilities can be discovered. We have to move even faster than before, especially with a codebase that's been around for over a decade. This means we're doubling down in a few important areas: * Proactive security: Strengthening our bug bounty programs, expanding AI-assisted vulnerability discovery/adversarial testing, and continuously improving testing across releases. This discovery reinforces why these investments matter. * Addressing legacy tech debt: Working with our internal red team, external security researchers, and the XRPL Foundation to revisit longstanding assumptions in critical areas like payments engine, consensus, and P2P networking, guided by an updated threat model. * Accelerating formal verification of critical areas: Continuing our work with CommonPrefix and the XRPL Foundation to apply formal verification to critical parts of the protocol, with the goal of uncovering deeper issues that other approaches could easily miss. We will build on the learnings from formal verification of the Lending Protocol and Single Asset Vault. * Systemic hardening: Moving beyond individual bug fixes to identifying latent risks in older parts of the XRPL codebase and eliminating entire classes of vulnerabilities. Our goal isn't simply to find more bugs. It's to systematically address the underlying risks and make the XRPL harder to exploit. As the XRPL's role in global financial infrastructure grows, so does our responsibility to protect it. Security is never finished. We'll keep investing and improving alongside the broader XRPL community. Full disclosure for the 3.4.1 release:

From roughly 1M in July to over 13M today, agentic payments on the XRP Ledger are compounding faster than most expected. The next phase is bringing more real-world merchants and services onchain, with agents paying in $XRP and RLUSD and settling on XRPL through @t54ai's x402 facilitator.

XRPL is now part of how the agentic economy transacts. Our x402 facilitator enables merchants to accept agent payments in XRP and RLUSD. With the XRPL AI Hub, developers can discover services, find integration resources and follow x402 payment activity. Together, these tools give developers a practical way to use the XRP Ledger for agentic commerce. More:

Today, we announced that we've completed our business combination with Armada Acquisition Corp. II. On Monday, our common stock is expected to begin trading on Nasdaq under the ticker $XRPN. I wrote down what I think the next five years could look like: I believe finance is about to look a lot more like tech. Full post: Not investment advice or an offer of securities. Contains forward-looking statements; actual results may differ materially. Risk factors:

Just a couple of months ago, I predicted XRPL would quickly surpass 10M agentic transactions. XRPL has now hit another milestone, processing over 13M with 166 x402 merchants. Agentic payments now account for roughly 25% of activity on the ledger. 100M might actually come sooner than we expect! Now is the time to build. Agents are already paying for APIs, data and compute. XRPL’s low fees, fast settlement, and growing AI toolkit give developers the tools to turn that demand into new products. 🚀

Today's vibe-coding project: a drag-and-drop builder for XRPL Batch transactions 🧱 Stack them up, sign, submit, and they land atomically. Every tx type comes straight from the node 🚀 (Obligatory “this isn’t production grade, use at your own risk”)

In the first hour of Batch being live on XRPL Mainnet: 1,275 Batch txs from 21 accounts, the first 29 seconds after activation. Already in use for atomic NFT swaps, swap + app fee in one tx, and RLUSD-funded fees, plus 1,200+ all-or-nothing arbitrage attempts.

I’ve had a few people write to ask me to follow up on a (reply!) tweet I wrote that’s gotten a lot of retweets. I considered deleting it just to avoid the headache, but I think that would make people more paranoid. So let me share my thoughts.

New paper on how to securely instantiate Fiat-Shamir using VRFs. This is a joint work with @RiddhiGhosal (Nokia Bell Labs) @aniketpkate (Mysten Labs) @pratyaycrypto (Hashgraph), and @sinharo (Hashgraph). The idea seems simple but the proofs are extremely complicated. Kudos to @RiddhiGhosal for taking the lead on that.

This is what's next for the XRP Ledger! RippleX Ayo at XRP Seoul on the 4 pillars for the next wave of XRPL adoption: 1. Trust - A resilient network and high security with formal verification and adversarial testing are fundamental for adoption. 2. Privacy - Institutions need compliant confidentiality, ZKP lets validators confirm a transaction without seeing its details. XLS-96 first step into this direction currently up for voting. 3. Scalability - More than tps especially with more users, infra load, we have to scale the XRPL for future demand. Starting with Batch. 4. AI - we are seeing a steady increase of agentic payments on the XRPL that leverage low cost settlement. Agents need identity and permission to safeguard what they can do.

About to leave South Korea 🇰🇷 ✈️ Extremely proud of what the XRP community here has built. A reminder that "the" community is so much more than your social media feed. People from all parts of society came to XRP Seoul. Crypto is part of their lives. Also glad we now have a regional hub in XRP Asia to support the many builders who showed up. One of my personal highlights was a long conversation with the blockchain lead at Kakao Bank at XRP Seoul. Kakao is basically the Korean WeChat. They have 27 million users and are starting to build their blockchain infrastructure in 2027. How they think about Custody, commodity assets like XRP and RWAs was insightful! Looking at every side of our ecosystem, I see us not only pushing past our goals, but also very talented people at the helm. Good feel. Really excited for what’s ahead. Bye Seoul 👋

🎤 @XRPSEOUL 2026 Highlights | Keynote “Building XRPL for the Next Wave of Adoption” What is being built into the XRP Ledger to support the next wave of developers, institutions and users. 🗣 Speakers: • Ayo Akinyele (@ja_akinyele), Senior Director of Engineering at @Ripple 🔎 Key Takeaways: 1️⃣ Fortifying Trust & Scalability for Complex Workflows To handle the growing demand of complex financial operations on-chain, the XRPL architecture is undergoing rigorous upgrades. This includes formal verification, adversarial testing, and new structural features like transaction batching, which enables bundled, all-or-nothing operations to boost system efficiency and developer scalability. 2️⃣ Unlocking Institutional Adoption Through Privacy Complete on-chain transparency has historically been a barrier for traditional finance. To solve this, the XRP Ledger is introducing "confidential transfers" powered by Zero-Knowledge Proofs (ZKPs). This allows institutions to keep their complex transaction workflows private while still proving their validity to the network and regulatory bodies. 3️⃣ Paving the Way for the AI Agent Economy AI agents are now driving massive network volume, recently crossing 11 million transactions on the XRPL. To securely support this rapid growth, Ripple is developing purpose-built agent infrastructure, including verifiable identities, strict execution safeguards (permissions and spending rules), and secure smart wallets capable of holding XRP and stablecoins with fast 3-5 second settlement. 💡 The Takeaway The next wave of XRP Ledger adoption extends far beyond simple human-to-human payments. By anchoring its engineering roadmap around four core pillars, Trust, Privacy, Scalability, and AI Agent support, Ripple is evolving the XRPL into a highly robust, institutional-grade network ready to power complex financial workflows, tokenized real-world assets, and the emerging autonomous machine economy. Hosted by @XRPLKorea

Welcome, @XRPAsiaOfficial! XRP Asia is live, and the XRP Ledger Foundation is glad to see a team focused on the Asia-Pacific community. They will foster that community across the region, drive XRP Ledger adoption, support builders, and nurture startups. APAC is already one of the most active parts of the XRP Ledger ecosystem. A local home for builders, founders, and communities should make that work easier to find, fund, and grow. We look forward to collaborating closely. Congratulations on the launch!

Excited to share that xrpld 3.3.0 is now available for the XRPL community to review! The release includes support for five proposed amendments that, if approved, would continue expanding the XRPL's capabilities for tokenized assets and real-world financial use cases. These proposals strengthen capabilities around privacy, settlement, operational controls, and asset management that become increasingly important as more financial assets move on-chain. As always, these amendments are not yet active. They will only activate following validator approval through the XRPL amendment process. Whether you're building on the XRPL, issuing tokenized assets, running infrastructure, or simply following the ecosystem, I encourage you to take a look. And if you run a validator, please review the release notes and specifications before voting. Let's build! 🚀

If you've ever tried to get three people to sign the same document at the same time, you already understand the problem this proposal is trying to solve. The XRP Ledger has supported multi-signature transactions for years. Multiple people can authorize an account, and a transaction only executes once enough approvals are collected. The challenge isn't the signature generation. It's coordinating them. Today, that coordination happens entirely off chain. Someone creates the transaction, shares it with every signer, collects signatures, assembles them, and submits the final transaction. That person becomes the single point of failure. If they go offline, lose a signature, or make a mistake, the whole process can stall or start over. The On-Chain Cosigner proposal moves that coordination onto the XRPL itself. A transaction is posted on the ledger as a proposal, and each signer adds their approval directly to the same object. The ledger validates every signature as it arrives. Once quorum is reached, the transaction is already fully signed, and anyone can submit it. No coordinator. No manual assembly. This is especially useful for institutions, custodians, and treasury teams where multiple people, or even multiple organizations, need to authorize the same transaction. The proposal is also designed to complement other work in progress, including batched transactions and lending flows that require approvals from multiple parties. Huge credit to Shawn Xie (@ShawnXie52472), Zhiyuan Wang, Chenna Keshava B S, and Mayukha (@msvadari) for putting this proposal together. We welcome community feedback!