What if / The smart contract changes / RLUSD

The smart contract changes — Ripple USD

Who can replace the code or create new tokens, and do the documents describe it?

As of 20 Nov 2026

Assumption: the contract code is replaced, or new tokens are minted.

Full passport of RLUSD ↗

Short answer

For Ripple USD, the archived documents answer 2 of 3 questions that matter for this event; 1 stay Unknown.

2 of 3 answered1 Unknown
01

What the documents say

Issuing new tokensConfirmed

Ripple may burn RLUSD in one wallet and mint new RLUSD into another if law or its compliance policies require it.

“(c) Ripple may burn (i.e., destroy) RLUSD held in a particular digital wallet and to mint new RLUSD into a different digital wallet at its sole discretion if required to do so by Applicable Law or Ripple’s internal compliance policies.”
Source: Standard Custody & Trust Company, LLC — TermsPublished: publication date not statedArchived: 23 Oct 2026Reviewed: 23 Oct 2026
✓ Quote found word for word in the latest snapshot
Freezing and blockingConfirmed

Ripple may freeze RLUSD by blacklisting an address if law or its internal compliance policies require it.

“(a) Ripple may freeze RLUSD by blacklisting a particular digital address rendering the associated digital wallet, which may be a User Wallet, restricted from transmitting or receiving RLUSD at its sole discretion if required to do so by Applicable Law or Ripple’s internal compliance policies.”
Source: Standard Custody & Trust Company, LLC — TermsPublished: publication date not statedArchived: 23 Oct 2026Reviewed: 23 Oct 2026
✓ Quote found word for word in the latest snapshot
02

What the contract shows

In the code: Replace the codeupgradeToAndCall(address,bytes)block 26454387, read 20 Nov 2026, 06:02 UTC
In the code: Create new tokensmint(address,uint256)block 26454387, read 20 Nov 2026, 06:02 UTC
In the code: Hand over controlgrantRole(bytes32,address)block 26454387, read 20 Nov 2026, 06:02 UTC
Contract code can be replaced (proxy)Yesblock 26454387, read 20 Nov 2026, 06:02 UTC
Current code (implementation)0x9747a0d261c2d56eb93f542068e5d1e23170fa9eblock 26454387, read 20 Nov 2026, 06:02 UTC

A function in the contract shows what is technically possible. It does not show what the terms allow, and the terms do not show what the code can do. AsOf shows both, side by side.

03

Contract and documents side by side

In the code: upgradeToAndCall(address,bytes). The documents we archive do not answer “Upgrading the contract”. This needs an explanation, not a conclusion.

Requires explanation The contract is an upgradeable proxy: its code can be replaced at the same address. The documents we archive do not answer “Upgrading the contract”.

?

What stays unknown

Can the RLUSD smart contract be changed?Unknown

The documents we archive don't answer this yet.

Q

Questions about Ripple USD

Can the RLUSD smart contract be changed?

The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.

Who can create new RLUSD tokens?

Ripple may burn RLUSD in one wallet and mint new RLUSD into another if law or its compliance policies require it. (Standard Custody & Trust Company, LLC)

Can RLUSD be frozen, and by whom?

Ripple may freeze RLUSD by blacklisting an address if law or its internal compliance policies require it. (Standard Custody & Trust Company, LLC)

Limits. This is a reading of public documents as of a date, not legal advice about anyone's situation. A quote shows what a document says; it does not show what an issuer or a court will do.

How to cite: AsOf, “The smart contract changes: Ripple USD (RLUSD)”, As of 20 Nov 2026 — https://asof.pro/en/what-if/contract-change/rlusd/

Other events for RLUSD: The price falls below its reference · The issuer stops redemptions · The issuer becomes insolvent · Tokens are frozen · The terms change · The backing becomes unreachable