RLUSD, Ripple's U.S. dollar-pegged stablecoin, is now live across more than 40 blockchains via Wormhole's Native Token Transfer (NTT) standard. The deployment marks a structural shift in how regulated stablecoins can operate across fragmented blockchain infrastructure: instead of creating wrapped token representations on each chain, NTT allows the original asset to be transferred while preserving its compliance properties natively.
The distinction matters for institutional adoption. Wrapped tokens introduce a second layer of trust — the wrapping bridge itself — between the original asset and its representation on a destination chain. A wrapped RLUSD on an EVM chain is backed by the bridge's custodial structure, not directly by Ripple's reserve. NTT removes that layer.
Wormhole's Native Token Transfer standard is designed for asset issuers who need to maintain custody and compliance control as an asset moves cross-chain. In a traditional bridging model, the original token is locked on its native chain while a synthetic representation is minted on the destination. The issuer loses direct control over the asset once it crosses the bridge.
Under NTT, the token issuer retains ownership of the token contract on each supported chain. Compliance metadata — including transfer restrictions, KYC/AML flags, and regulatory hold capabilities required for regulated stablecoin issuers — travels with the asset through every transfer, enforced by the issuer's own contract logic rather than delegated to a bridge operator.
RLUSD's deployment via NTT means compliance travels with the asset natively. A transfer restriction that applies on XRP Ledger applies equally when that RLUSD moves to an EVM chain — the stablecoin's regulatory wrapper is not lost at the bridge boundary.
The Wormhole network currently supports more than 30 chains across its messaging layer, with NTT deployments available across major EVM chains, Solana, and other ecosystems. The RLUSD deployment covers the full scope of Wormhole's supported chain list, making RLUSD natively available for settlement, collateral, and payment use cases across the broad multi-chain ecosystem — not limited to XRP Ledger and Ethereum where RLUSD first launched.
For DeFi protocols and institutional applications operating on non-EVM chains or newer ecosystems, RLUSD availability via NTT creates access to a regulated stablecoin without relying on third-party bridge operators or wrapped token proxies. The stablecoin's NYDFS-regulated status and dollar peg remain intact regardless of which chain it's deployed on.
The RLUSD + NTT combination directly benefits builders on XRP Ledger who need cross-chain interoperability without giving up the compliance properties that institutional clients require. A tokenized asset issued on XRPL can now be paired with an RLUSD settlement leg that travels natively across chains — without the counterparty risk of a wrapped token bridge in between.
This positions RLUSD as a candidate settlement asset for cross-chain RWA workflows, where an asset might be issued on XRPL's regulated ledger infrastructure but settled against RLUSD collateral that a counterparty holds on an EVM chain. That workflow previously required either wrapping or separate liquidity pools on each chain.
For context on how RLUSD fits within the broader XRPL stablecoin landscape, see our analysis of RLUSD crossing $1B in supply and the institutional stablecoin dynamics it reflects.