RLUSD security-first bridges vs KelpDAO bridge failure

Ripple CTO David Schwartz says RLUSD uses a “security-first” cross-chain model, arguing bridge failures come less from interoperability itself and more from teams cutting safeguards for convenience. He cites the April 18 KelpDAO/rsETH incident: a LayerZero-based setup with a 1-of-1 DVN enabled message spoofing, letting attackers mint fake rsETH and drain about $292M. Aave then froze rsETH and wrsETH markets, stopping new deposits and new borrows while pools stayed live. Schwartz contrasts this with RLUSD, which is issued natively on the XRP Ledger and Ethereum, reducing the need for a high-risk single bridge layer. Ripple uses Wormhole’s Native Token Transfers (NTT) to enforce multi-layer verification and stricter control over token issuance. On the market side, RLUSD was approved as futures collateral on Bitrue, potentially improving capital efficiency. Ripple is also reported to be discussing RLUSD integration with Mastercard for more direct settlement between traditional finance and blockchain rails. For traders, RLUSD’s narrative now links tightly to cross-chain risk discipline after a major bridge exploit. If the market believes RLUSD’s architecture reduces “bridge blowup” probability, sentiment could improve; if not, interoperability-linked tokens may remain sensitive to similar failures.