SKIP TO CONTENT
TOKENIZATION6 minBuilding the RWA Chain · Episode 5

GENIUS Act: Freezing Stablecoins Without an All-Powerful Key

A court orders an issuer to freeze, then burn, one holder’s coins. Who should be able to press that button, and could one stolen key do it?

Pixel-art night scene of a vault control room with three separate levers, each with its own keyhole. An ice-blue freeze lever, a magenta order lever, and an ember burn lever under a glass cover with an hourglass. A cracked giant golden key lies on the floor.

IN 30 SECONDS

A lawful order, under the US GENIUS Act, is a final court or federal agency order to seize, freeze, burn or block specific stablecoins. Issuers must be technically able to obey one. Here is my proposed way to do it without one all-powerful key, as a reading of the law, not legal advice.

KEY TAKEAWAYS

· 3
  • Under the GENIUS Act, a lawful order can require an issuer to seize, freeze, burn or block specific stablecoins. The issuer must be technically able to comply.
  • One key that can freeze, burn and hand out new powers is the risk: whoever holds it, or steals it, can do all three.
  • My proposed design, not audited: one role per action, with burns delayed and executed by another account. Every order action carries an order reference, and each role sits in a multisig.
On this page

One key that can do everything is the risk

IN SHORT The easy way to obey a freeze or burn order is one key that can do everything, and that key becomes the risk.

WORDS TO KNOW

Lawful order
A final, valid order under federal law, from a competent court or authorized federal agency. It makes an issuer seize, freeze, burn or block specific stablecoins. It can be appealed.
Freeze
Blocking an address so its holder can’t transfer the tokens; privileged actions such as a burn still can. The block can be lifted later.
Burn
Destroying tokens held at an address. Unlike a freeze, it can’t be undone.
Multisig
A shared account that acts only when several of its key holders sign, for example 3 of 5.

The GENIUS Act is the US federal law on payment stablecoins, approved on 18 July 2025. One of its sentences lands straight on the token’s smart contract, the program on the blockchain that records balances.

A permitted issuer can issue payment stablecoins only if it can technically comply with a Lawful order A final, valid order under federal law, from a competent court or authorized federal agency. It makes an issuer seize, freeze, burn or block specific stablecoins. It can be appealed. See the glossary. Such an order can demand a Freeze Blocking an address so its holder can’t transfer the tokens; privileged actions such as a burn still can. The block can be lifted later. See the glossary. It can also demand a Burn Destroying tokens held at an address. Unlike a freeze, it can’t be undone. See the glossary.

IN PLAIN WORDS

The tempting shape is one admin key that freezes, burns and appoints new agents. People call it a god key.

Whoever holds that key, or steals it, can freeze or burn anyone’s coins, and a burn is final.

ADAM says: Think of a bank vault: a hold on an account is quick, but the vault needs two staff and a time lock. Where it breaks: a clerk reads the court order, a contract never can.

Full disclosure: I built ERC-3643’s token suite at Tokeny. The design below is my proposal.

Coming up next: So how do you obey an order without that key?

How to freeze or burn without one admin key

IN SHORT Put one controller contract in front of the token and give each power its own role: freezes go fast, burns wait.

The controller is the only account the token lets freeze or burn, provided the token’s Owner, who can appoint agents, is locked down too. Ideally each role is held by a different Multisig A shared account that acts only when several of its key holders sign, for example 3 of 5. See the glossary. Two roles are still two accounts, not necessarily two people.

PROPOSED ORDER FLOW

Flow diagram: 6 stepsFlow diagram: 6 steps. Order checked off-chain, then Order registered. Order registered, then Holder frozen. Holder frozen, then Burn queued. Burn queued, then 48-hour wait. 48-hour wait, then Burn executed by another account.1Order checked off-chain2Order registered3Holder frozen4Burn queued548-hour wait6Burn executed by anotheraccount

Step 1. Review. Legal checks the order off-chain: final, valid, specific? The contract never reads the order itself.

Pick a step to see it move
  1. Review Legal checks the order off-chain: final, valid, specific? The contract never reads the order itself.
  2. Register The registrar role logs the order reference, a hash (short fingerprint) of its identifier, in public.
  3. Freeze The freezer role freezes the named address at once: a freeze can be undone.
  4. Queue The proposer role queues the burn, accepted only if the order is active and the address frozen under it.
  5. Wait A 48-hour delay runs. If the order is stayed (put on hold) or lifted, the burn can be canceled.
  6. Proposer: refused If the account that proposed this burn tries to execute it, the code refuses, burn by burn.
  7. Execute Another executor runs it, only if the order is still active and the holder still frozen.
My proposed sequence for one order that ends in a burn. A design sketch: not audited, and not a feature of ERC-3643’s reference code.

Every order action carries the order reference, so the chain shows which order justified which action.

WATCH OUT

This sketch doesn’t check the order’s scope. Which holders and amounts it covers is verified off-chain before anyone signs. Nothing in the contract binds a reference to a holder or a cap.

The 48 hours is a timelock, a wait the contract enforces. It’s a placeholder, not a number from the Act or the proposal. Pick it with counsel: long enough to catch a mistaken or stayed order, short enough to meet what the order demands.

ITEM GET

Freeze fast, burn slow

A freeze can be undone, so it runs at once. A burn is final, so it waits, and another account executes it.

Coming up next: What does that wait buy if the order is overturned?

One order, one burn, one appeal

IN SHORT The delay is what lets an order lifted on appeal stop a burn that was already queued.

A WORKED EXAMPLE

Illustrative numbers

PASSAn order to freeze and burn one holder’s coins

INPUT

Order
ref 0x7c1e...a2f0 (hash of its identifier)
Holder
0xA11c...91e0
Amount
10,000 units
Delay
48 hours (placeholder)

WHAT HAPPENS

  1. Legal reviews the order off-chain, then the registrar registers its reference.
  2. The freezer freezes the holder under that order.
  3. The proposer queues a burn of 10,000 units.
  4. 48 hours later, a different account with the executor role runs it. The order is still active and the holder still frozen.

OUTPUT

Result
10,000 units burned
Record
each controller event carries the order reference

STOPPEDSame order, lifted on appeal during the delay

INPUT

Event
order lifted on day 1

WHAT HAPPENS

  1. The registrar marks the reference Lifted. A lifted reference can never be reused.
  2. After 48 hours, the executor tries the burn. The contract refuses: “order not active”.
  3. The freezer releases that order’s freeze, which only works once the order is lifted.

OUTPUT

Result
nothing burned; unfrozen if no other order applies

PART COMPLETE

What you now know

  • Why one key that can freeze, burn and hand out powers is the risk behind an order.
  • How my proposed controller splits one order into steps, each for its own role.
  • Why the delay lets an appeal stop a burn that was already queued.

Check yourself

Tap or click a question to see the answer.

The account that queued a burn is later given the executor role too. After the 48 hours, can it run that burn?

No. The code records who proposed each burn and refuses if that same account tries to execute it, even after a role change.

Next part:What does the GENIUS Act require an issuer to be able to do, and what does the Fed’s proposal add?6 min
Adam Boudjemaa
Adam Boudjemaa

Web3 x AI engineer, former CTO of Integra. Named author (1 of 5) of ERC-3643, first author of ERC-6960, co-author of ERC-7410, and co-author of ERC-8203, which is still a draft.

Have a project to ship or a role to fill?

Discuss your project or role

My work at the web3 x AI intersectionOpen-source tools I build

Follow the engineering notes

Get new articles on production AI and smart contracts by email.