HomeWho it’s forIssuers & banks
Keep control. Keep your options open.
Enforce the offering’s rules without tying the asset to one vendor.
Today, and with ERC-3643.
Today
The rules live in documents.
With ERC-3643
The token enforces them itself.
How it works
- Function
canTransfer(), checked on every transfer- Who acts
- Automatic.
- Recorded
- Failed transfers never settle.
Today
One vendor’s format locks you in.
With ERC-3643
A public standard any platform can read.
How it works
- Function
- The
IERC3643interface - Who acts
- Any platform that supports it.
- Recorded
- —
Today
Wallets and venues must support you.
With ERC-3643
It’s ERC-20 compatible, so existing tools work.
How it works
- Function
IERC3643extendsIERC20- Who acts
- —
- Recorded
- Standard
Transferevents.
Today
Who can act on the asset?
With ERC-3643
You appoint and remove the agents.
How it works
- Function
addAgent(),removeAgent()- Who acts
- The owner, as defined by ERC-173.
- Recorded
AgentAdded,AgentRemoved.
Today
Corrections need every party.
With ERC-3643
Your agents can freeze, recover and correct.
How it works
- Function
setAddressFrozen(),recoveryAddress(),forcedTransfer()- Who acts
- An agent of the token.
- Recorded
- Every action emits an event.
What stays the same
The standard doesn’t make an offering compliant. It enforces the rules you and your advisers set.
Questions you’ll be asked
Who owns the token contract?
The issuer, or whoever it designates, as owner under ERC-173.
Can we move to another platform later?
Yes. The token follows a public interface, so another platform that supports ERC-3643 can operate it.
Which networks can we issue on?
Ethereum or any EVM-compatible network, including layer 2s, using the reference code. The standard isn’t compatible with non-EVM chains.
