SKIP TO CONTENT
TOKENIZATION6 minBuilding the RWA Chain · Episode 5

GENIUS Act Lawful Orders: The Law and the Fed’s Proposal

The law asks for the capability to obey any lawful order, and names no design. So what exactly must your code be able to do?

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

Section 4(a)(6)(B) is a GENIUS Act clause on permitted issuers. They may issue payment stablecoins only if they can technically comply, and will comply, with any lawful order. The Fed’s September 2026 proposal adds no rule for it, but would cover smart contracts and private keys.

KEY TAKEAWAYS

· 3
  • Under section 4(a)(6)(B), an issuer may issue payment stablecoins only if it can technically obey any lawful order, and will.
  • A lawful order names specific coins or accounts with reasonable particularity and can be appealed. The Act prescribes no contract design.
  • The Fed’s 29 September 2026 proposal adds no rule for that clause but would cover smart contracts and private keys. Not a final rule: comments close 30 November 2026.
On this page

What does the GENIUS Act require an issuer to be able to do?

IN SHORT The Act requires the capability to comply with the terms of any lawful order. It does not prescribe a contract design.

WORDS TO KNOW

Payment stablecoin
Simplified: a digital token meant for payment. Its issuer must redeem it for a fixed sum, such as one dollar, and presents it as holding a stable value.
Proposed rule
A draft regulation published for public comment. It can change before the final rule.
Self-executing
Said of a clause that applies on its own, with no extra rule from a regulator.

The key sentence is section 4(a)(6)(B) of Public Law 119-27, the GENIUS Act itself. A permitted issuer of Payment stablecoin Simplified: a digital token meant for payment. Its issuer must redeem it for a fixed sum, such as one dollar, and presents it as holding a stable value. See the glossary:

may issue payment stablecoins only if the issuer has the technological capability to comply, and will comply, with the terms of any lawful order.

Section 4(a)(6)(B), Public Law 119-27

Two words matter for engineers: capability and terms. The order sets the scope, and your code must be able to execute exactly that. That’s my reading, not legal advice.

THE DEFINITION, SEC. 2(16)
A lawful order, sec. 2(16)
Who issues itcourt or authorized Federal agency

A final and valid order issued under Federal law

What it ordersseize, freeze, burn or prevent transfer

Clause (A): what your contract must be able to do

Which coinsstablecoins or accounts

Clause (B): named “with reasonable particularity”. Encoding that per address, and per amount where the order sets one, is my design choice

Appealappealable

Clause (C): subject to judicial or administrative review or appeal, so reversibility matters

The four parts of a lawful order, as the Act defines it.

Coming up next: So does the Fed’s proposal say how to build it?

What the Fed’s proposal says about smart contracts and keys

IN SHORT The Fed’s proposal adds nothing on how to freeze, but it does cover the code and the keys, and it’s still only a proposal.

The Federal Reserve Board published its Proposed rule A draft regulation published for public comment. It can change before the final rule. See the glossary on 29 September 2026 (91 FR 61580, Docket R-1899). It covers the issuers the Fed supervises.

WHERE THINGS STAND

Flow diagram: 5 stepsFlow diagram: 5 steps. Act approved: 18 July 2025, then OCC, FDIC, NCUA proposals: 2026. OCC, FDIC, NCUA proposals: 2026, then Fed proposal: 29 September 2026. Fed proposal: 29 September 2026, then Comments close: 30 November 2026. Comments close: 30 November 2026, then Act applies: 18 January 2027 at the latest.1Act approved: 18 July20252OCC, FDIC, NCUAproposals: 20263Fed proposal: 29September 20264Comments close: 30November 20265Act applies: 18 January2027 at the latest

Step 1. Law. The Act becomes law.

Pick a step to see it move
  1. Law The Act becomes law.
  2. Other regulators Three other federal regulators publish theirs earlier.
  3. Fed proposal The Fed publishes its proposal.
  4. Comments Public comments close. The text can still change.
  5. In force Section 20: 18 months after enactment, or 120 days after final regulations if sooner.
Dates from the Act (sec. 20) and the Fed’s proposal.

On lawful orders, the proposal lists section 4(a)(6)(B) among the Act’s “self-executing provisions that are not addressed in this rulemaking.”

IN PLAIN WORDS

The Fed reads that clause as Self-executing Said of a clause that applies on its own, with no extra rule from a regulator. See the glossary: it applies on its own, so the Fed writes no extra rule for it.

Sec. 247.13(b)(3)(iii)
Processes to ensure key systems and controls, “including smart contracts, are operating as intended”
Sec. 247.13(b)(3)(iv)
Periodic independent testing
Sec. 247.13(b)(6)
Secure handling of digital assets, “including private key management, backup, and recovery”
Definition of “private key”
Intended to include shards of a private key
Question 126
Asks whether the rule should “expressly address risks relating to smart contracts”

[An issuer’s] ability to safeguard minting, burning, and freezing of payment stablecoins depends on the integrity of its smart contracts, including the associated private keys.

The Fed’s proposed rule, preamble

WATCH OUT

All of this is proposed text. It can change before a final rule. Comments close on 30 November 2026.

ITEM GET

Code and keys are in scope

My reading: if adopted as proposed, Fed-supervised issuers would need to check their contracts work as intended and guard their keys.

FAQ

Section 4(a)(6)(B): the issuer must be able to comply with any lawful order, and will comply. Such an order can require seizing, freezing, burning or blocking coins.

Section 4(a)(5)(A)(iv) also asks for “technical capabilities, policies, and procedures to block, freeze, and reject specific or impermissible transactions” that break federal or state law. Neither sets a contract design. This is a reading of the text, not legal advice.

It would ask the issuers it supervises to check that key controls, “including smart contracts, are operating as intended”, with regular independent tests. It would also cover private key backup and recovery.

Its private key definition is intended to include shards. It’s a proposal, not a final rule.

PART COMPLETE

What you now know

  • What makes an order a lawful order under the Act: who issues it, what it can demand, and that it can be appealed.
  • Why the Fed’s proposal adds no rule on lawful orders but still reaches smart contracts and private keys.

Check yourself

Tap or click a question to see the answer.

An issuer splits its burn key into 3 shards held by 3 people. Does that take the key out of the Fed’s proposed key rules?

No. The proposed definition of a private key is intended to include shards, so splitting doesn’t take it out of scope.

Next part:Does the ERC-3643 reference token already split freeze and burn, and how do you check your own setup?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.