It built its burn transaction against a superseded QUSD contract, so a redemption started here could not settle. It is kept out of service rather than left to take a burn that the settlement service would then refuse.
Go to the live redemption pageThe live page reads the burn target, selector, token decimals and calldata from the redeem service's own preflight response, so it always addresses the contract that chain actually settles.
If you hold QUSD on the XRP Ledger instead, the Xaman flow is at https://qusd.quantvestrix.io/redeem — that is the XRPL rail, not this one. (Absolute on purpose: a relative /redeem is 404 on qvtx.quantvestrix.io, one of the hosts this stub is served from — measured 2026-10-14.)
Retired 2026-10-14. Superseded contract: 0x63C4664CeB3e93ef22d1E56826395Fb1C927C118
— selector 0x47cdbec2. Nothing you do on this page can send a transaction.