The Wallet Standard AI Agents Were Missing Just Got a Hackathon

RippleX joins MoonPay’s Open Wallet Standard Hackathon with XRPL and RLUSD challenge tracks targeting agentic finance and x402 on-chain settlements. Register April 3.

RippleX confirmed it is joining MoonPay’s Open Wallet Standard Hackathon with dedicated challenge tracks on the XRP Ledger. The event runs April 3 across San Francisco, New York, Miami, and remotely. Builders working at the intersection of AI agents and on-chain payments are the target audience.

According to @RippleXDev on X, the team is bringing XRPL and RLUSD challenge tracks specifically focused on AI agents in finance. The post stated builders targeting the intersection of AI agents and on-chain payments should come hack with them. Registration is open at hackathon.openwallet.sh.

What Builders Are Actually Competing to Build

MoonPay confirmed on X that both MoonPay and Ripple are looking for builders in the OWS Hackathon. The challenge categories include Agentic Payments, Agentic Commerce, Wallets, Identity, and Guardrails, and Settlement Infrastructure. Products using x402, RLUSD, or the XRP Ledger are all in scope.

The hackathon sits on top of MoonPay’s Open Wallet Standard, which the company launched on March 23. Per the official press release, the OWS gives AI agents a universal, secure way to hold value, sign transactions, and pay across every major blockchain without ever touching a private key. Ripple was among the over 15 contributing organizations at launch, alongside PayPal, OKX, Tron, TON Foundation, Solana Foundation, Ethereum Foundation, and others.

MoonPay CEO Ivan Soto-Wright put it plainly in the announcement. The agent economy had payment rails. What it lacked was a wallet standard. MoonPay built one, open-sourced it, and the full stack now exists, he said.

XRPL and RLUSD as the Settlement Layer

The XRPL challenge tracks carry real technical weight. The Open Wallet Standard already derives XRP Ledger accounts from a single seed phrase, making XRPL a native part of its multi-chain signing interface. When an x402 payment request comes in, OWS produces the signed authorization using a policy engine that checks spending limits before any key is touched.

That x402 connection matters more now. The x402 protocol recently moved to the Linux Foundation with backing from Amazon Web Services, Google, Microsoft, Visa, Mastercard, and Stripe, cementing it as the emerging standard for machine-driven transactions on the internet. RLUSD, Ripple’s regulated stablecoin, sits directly in that settlement pipeline on XRPL.

The settlement infrastructure track is where RLUSD becomes most relevant. Agents running on OWS can hold RLUSD balances, receive x402 payment requests for compute or data, and settle on-chain without any human in the loop. The whole flow stays inside the OWS vault structure.

The Bigger Context Builders Should Know

The wallet problem OWS is solving is not small. Before the standard, every agent framework handled key management differently. No portability. Private keys ended up in environment variables and plaintext config files. A wallet built for one agent could not be used by another.

OWS changes that. One encrypted vault on the user’s machine. One interface across eight chain families including EVM, Solana, Bitcoin, TON, Tron, Filecoin, and XRP Ledger. Keys are encrypted at rest using AES-256-GCM, decrypted only to produce a signature, held in protected memory, and wiped immediately after. The agent never sees the private key.

Not everyone is convinced the timing is perfect though. A Dragonfly executive recently warned that agentic payments remain firmly in the experimental stage, with x402 processing roughly one million dollars in daily volume. The early majority, he argued, is still years away.

Still, RippleX’s participation signals the XRPL community is not waiting. The hackathon gives builders a direct path to test RLUSD and XRPL inside a live agent payment stack with institutional-grade infrastructure behind it.

The OWS standard is MIT-licensed and available now. Node.js and Python SDKs are live on npm and PyPI. Source code is at github.com/open-wallet-standard.