XRPL Testnet demo · no real value
RLUSD cannot be escrowed today
Ripple’s official RLUSD issuers have escrow locking switched off on both networks, so no RLUSD can be locked in an escrow until Ripple opts in. We show the ledger’s verdict before anyone signs.
The same spikes found that a visitor can allow escrow creation alone and revoke it, that a Batch makes two escrows atomic, and that the outer Batch reports success even when its inner transactions roll back. Five upstream items with transaction hashes and three patches are ready to file. Spike evidence · Filing bundle.
Working examples reveal the gaps between a protocol feature and an integration a builder can use. Our builder feedback log keeps the observations, workarounds and mainnet implications.
Does the RLUSD issuer allow escrow?
Recorded unsigned rippled probes returned tecNO_PERMISSION for RLUSD EscrowCreate on Testnet and Mainnet; the matched TEST-SGD control returned tesSUCCESS on Testnet. Nothing signed or submitted. Read the verdicts and ledger indexes.
The live check below reads today’s validated AccountRoot for AllowTrustLineLocking; it does not simulate, submit a transaction or connect a wallet. A permission change still requires funding, trust-line, escrow and verifier requalification.
If off, tokens from that issuer cannot be locked in escrow. If on, that permission is enabled; amendment support, trust lines, freezes and other transaction rules still apply.
Not checked yet. Select “Check public ledgers” for current results.
Source: Ripple’s issuer addresses · AccountRoot flag: 0x40000000 (1073741824).
Read the feedback entry · Upstream draft: issuer permission preflight (draft, not a filed issue).
Checks contact public Testnet and mainnet servers in your browser. Mainnet access here is read-only.