ERC-3643 Freeze and Burn Powers: How to Review Them
In ERC-3643’s reference token, one Agent can freeze, burn, mint and pause. Is that your setup, and who can appoint a new Agent?

IN 30 SECONDS
T-REX is the reference code for ERC-3643, a token standard for securities. In its token, one Agent role can freeze, burn, mint, force transfers and pause, and the Owner can appoint new Agents. Below, I review those powers one question at a time.
KEY TAKEAWAYS
· 3
- In the T-REX reference token for ERC-3643, freeze, forced transfer, recovery, mint, burn and pause all sit behind one check, onlyAgent. The Agent is separate from the Owner, but one Agent holds every one of those powers.
- The Owner can always appoint a new Agent, so securing the Agent alone isn’t enough.
- My review is a heuristic, not a regulatory test: no standard makes a stablecoin compliant on its own.
On this page
How ERC-3643’s reference token gates freeze and burn
IN SHORT In the ERC-3643 reference token, one Agent role holds every power an order needs.
WORDS TO KNOW
- Agent
- In ERC-3643, an address appointed to run the token’s admin actions, such as freeze and burn.
- Owner
- The account that controls a token’s settings and can appoint or remove Agents.
- Timelock
- A wait the contract itself enforces before an action can run.
IN PLAIN WORDS
ERC-3643 is an Ethereum standard built for security tokens (shares, for example) that only approved holders can hold. It isn’t specific to stablecoins, but it already has every operation an order can demand.
In T-REX’s Token.sol, the reference code, freeze, forced transfer, recovery, mint (creating tokens), burn and pause all sit behind one check, onlyAgent: only an Agent In ERC-3643, an address appointed to run the token’s admin actions, such as freeze and burn. See the glossary can run them, batch versions included.
The Agent is separate from the Owner The account that controls a token’s settings and can appoint or remove Agents. See the glossary, who keeps settings such as the compliance rules. That separation is real. But the Owner can always appoint a new Agent (addAgent is onlyOwner), so securing the Agent alone isn’t enough.
ITEM GET
Lock the Owner down too
The repo also ships an optional AgentManager. As the token’s Agent, it splits callers into Freezer, Supply Modifier, Transfer Manager and Recovery Agent roles. A step in the right direction, though mint and burn still share one role and pause sits with the Freezer.
Coming up next: So what does a controller that splits every power check?
What the controller sketch checks before a burn
IN SHORT The sketch: a short Solidity contract, four operational roles plus an admin, a 48-hour placeholder delay and an order reference on every order action.
It compiles with solc 0.8.34, the Solidity compiler, and uses OpenZeppelin Contracts 5.1.0. Its 8 Foundry tests pass against a mock, a stand-in token that mirrors T-REX’s onlyAgent gate. It isn’t audited and it isn’t part of T-REX.
BEFORE ANY BURN
Step 1. Request. An executor asks to run a burn that’s still queued.
- Request An executor asks to run a burn that’s still queued.
- Delay 48 hours passed? If not: “still timelocked”.
- Proposer Not the proposer? Each burn stores its proposer, so a role change can’t get around this.
- Order Order still active? A lifted order blocks its queued burns.
- Unfrozen: refused Holder unfrozen outside the controller? The code refuses: “holder no longer frozen”.
- Burn These checks pass: the token burns the amount.
WATCH OUT
The admin can cancel a queued burn, so it should itself be a timelocked multisig, never a laptop key.
The controller counts freezes per holder: if two orders freeze one address, lifting one keeps it frozen until the other is lifted and released too.
Coming up next: How do you check a real setup against all this?
What I’d check before trusting the controls
IN SHORT Walk the controls one question at a time: every branch that ends in one key is a finding.
The tests I’d want in CI, run on every code change:
- a freezer can’t burn;
- a proposer can’t execute its own burn, even after a role change;
- a made-up or still-active reference can’t release a freeze;
- a lifted reference can’t be reused;
- the Owner can’t freeze or burn without passing through its own Timelock A wait the contract itself enforces before an action can run. See the glossary.
Run them against your real token deployment, not just a mock, because the proposal talks about controls “operating as intended”.
Sources: GENIUS Act, Public Law 119-27, Federal Reserve proposed rule, 91 FR 61580, T-REX Token.sol, T-REX AgentManager.sol.
FAQ
My proposal: a controller contract as the token’s only privileged caller. One role per action, each in a multisig. Every burn delayed, then run by an account other than its proposer.
Secure the token’s owner the same way: whoever can appoint agents can bypass the controller.
No standard does that on its own, and I won’t claim it. ERC-3643 standardizes interfaces for freezing, forced transfer, recovery, minting and burning on a permissioned token.
Whether an issuer meets the Act depends on its licensing, its supervisor and the facts, which is a legal question. The token layer is one piece of evidence that the capability exists.
PART COMPLETE
What you now know
- Why securing the Agent alone isn’t enough while the Owner can appoint new ones.
- Which checks my sketch runs before a burn.
- How to review a setup, knowing it isn’t a legal test.
Check yourself
Tap or click a question to see the answer.
A holder is frozen under orders A and B. A is lifted on appeal and its freeze released. Can the holder move coins now?
No. Freezes are counted per holder, so the address stays frozen until B is lifted and released too.
You finished every part published so far in this series. Back to the series page
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 roleMy 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.