How to Create an ERC-1400 Token: Steps and Audit Checklist
Part of our guide to digital asset security for banks

Quick answer. Choose a partition model, then implement ERC-20 plus the ERC-1400 drafts: ERC-1410 partitions, ERC-1594 transfer checks, ERC-1643 documents and ERC-1644 controller operations. Map every privileged role to a protected key, threshold or timelock, and audit each transfer path separately.
Video transcript
There is no single ERC-1400 contract to copy. It is a draft umbrella over four standards, and you own every gap they leave.
ERC-1410 adds partitions. ERC-1594 adds transfer checks, issuance and redemption. ERC-1643 links documents, and ERC-1644 allows forced transfers. All remain drafts, and ConsenSys's reference code is archived.
Build in order. Model the asset and its partitions, implement ERC-20 plus all four drafts, define reason codes, wire issuance and redemption, then anchor documents.
Fix the accounting early. Partition balances must sum to each holder's total, and total supply must count every token.
Run the transfer check and the real transfer through one validation function, or the check can say yes while the transfer reverts.
Map every privileged role to a protected key. Put the issuer behind a capped multisig, the controller, which can force transfers, on a separate multisig, isolate the certificate signer, and timelock upgrades.
Audit each path separately: transfers, partition and operator moves, issuance, controller calls, documents and upgrades. Then match deployed bytecode to the audited commit per chain.
ERC-3643 is Final and builds in identity and compliance. Its mint and forced transfers bypass compliance rules, so test them like ERC-1400 controller calls.
Read the full checklist, or talk to Guardian. Our audit puts two independent teams on one scope and fuzzes partition, supply and role invariants.
What ERC-1400 Is
Learning how to create ERC1400 token contracts starts with a surprise: there is no single contract to copy. ERC-1400 is an umbrella that points to four component drafts.[1]
The umbrella was created on September 9, 2018, and is still marked Draft. So are its parts.[2, 3, 4, 5]
ConsenSys's public implementation, UniversalToken, has been archived and read-only since March 25, 2025. Treat it as reference code, not a maintained baseline.[6]
That leaves your team owning every choice the drafts leave open, and every bug in those choices.
On top of ERC-20 compatibility, the umbrella requires a way to ask why a transfer would fail, forced transfers, standard issuance and redemption events, metadata on parts of a balance, and queryable documents. Transfers may also carry signed data.
| Draft | What it adds | Core functions |
|---|---|---|
| ERC-1410 | Partitions of a balance, and operators | transferByPartition, operatorTransferByPartition, partitionsOf |
| ERC-1594 | Transfer checks, data transfers, issuance and redemption | canTransfer, transferWithData, issue, redeem |
| ERC-1643 | Documents linked to the token | setDocument, getDocument, removeDocument |
| ERC-1644 | Forced transfers and redemptions | isControllable, controllerTransfer, controllerRedeem |
Implementation Steps
Build in this order. Each step fixes a decision the next one depends on.
First, model the asset. ERC-1410 gives each partition a bytes32 key and its own balance, so decide what a partition means: a tranche, a share class or a lockup state.[2]
Then pick a default partition rule. ERC-1410 calls partition selection on a plain transfer an implementation detail, so write down which partitions a transfer or redemption draws from, in what order.
Fix the accounting invariant early. The draft requires a holder's partition balances to sum to balanceOf, and totalSupply to count every token.
ERC-1410 also warns that looping over a holder's partitions must respect block gas limits. Cap partitions per holder, or keep loops out of transfer paths.
Second, implement ERC-20 plus all four component drafts; ERC-1400's IERC1400 interface combines them. ERC-1400 lists ERC-777 compatibility as optional.[1]
Your ERC-20 base carries the usual token bugs, and hooks add reentrancy. Our ERC-20 vulnerabilities guide covers both.
Third, define reason codes. canTransfer returns an ERC-1066 status byte and an application-specific bytes32 reason. canTransferByPartition also returns the destination partition.[3]
Route the view and the real transfer through one validation function. Otherwise the preflight can say yes while the transfer reverts, or the reverse.
Fourth, wire issuance and redemption. issue and issueByPartition add supply; redeem, redeemFrom, redeemByPartition and operatorRedeemByPartition remove it. Each emits Issued or Redeemed, or the ByPartition version.
Once isIssuable returns false, it must stay false and block all issuance. Use it to close a fixed-size offering for good.
Fifth, anchor documents. setDocument stores a name, a URI and an optional hash, with a last-modified timestamp, and emits DocumentUpdated. Always set the hash, so anyone can verify the file.[4]
Transfer Restrictions and Controllers
Last come the privileged roles. They decide who can move tokens without the holder.
ERC-1594 standardizes how to ask whether a transfer is allowed, not the rules behind it. Eligibility, lockups and investor caps are your code.[3]
transferWithData and transferFromWithData carry a bytes field for offchain data. ERC-1594 describes co-signing, where signed data from an authorized party approves the transfer.
The draft sets no certificate format. Signer binding, expiry, nonces and replay protection are yours to specify.
Bind each approval to the function, sender, receiver, amount, partition, chain ID and contract address. Add an expiry and a nonce, and reject any reuse.
Recover signers with a library that blocks signature malleability. Otherwise a check on used signatures can be passed with a second valid signature.
ERC-1410 lets a holder approve an operator for all partitions or for one. isOperatorForPartition returns true under either scope.[2]
Test revocation in both scopes. ERC-1410 warns that an operator whose all-partition grant is revoked may keep a per-partition grant.
ERC-1644 adds controllerTransfer and controllerRedeem. An authorized address can move or burn any holder's tokens, for legal action or lost keys.[1, 5]
Controller calls must respect balances, and may also need to respect other restrictions. The draft leaves that choice, and how controllers are authorized, to you.
Once isControllable returns false, it must stay false, and both controller functions must revert. Decide in advance what event switches control off.
The drafts define no pause or freeze functions, though ERC-1400 lists a reason code for a paused contract. If you add them, guard every path; our emergency pause design guide covers scope and who can unpause.
- Issuer: holds issue and issueByPartition, behind a multisig with a cap per call.
- Controller: forced moves only, on a separate multisig with logged legal approval.
- Certificate signer: an isolated key with rotation and an onchain revocation path.
- Document updater: cannot issue, move or upgrade anything.
- Pauser: can pause fast; a slower, stronger role unpauses.
- Upgrade admin: behind a timelock, so holders see changes before they land.
ERC-1400 Security Checklist
A security token has many doors. Audit each callable path on its own, asserting supply, partition and role invariants before and after every call.
The paths to cover: transfer, transferFrom, both data variants, partition and operator transfers, issue, redeem, controller calls, document updates, upgrades and migrations.[1, 2, 3, 4, 5]
Upgrades deserve their own pass. A new implementation could reopen issuance or control that a one-way flag had closed.
Lock every implementation's initializer too; our guide to initializer vulnerabilities shows how open ones get taken over.
Then compare deployed bytecode and configuration with the audited commit, on every chain you deploy to.
| Check | Evidence to ask for | Red flag |
|---|---|---|
| Partition accounting | Fuzzed invariant: partitions sum to balanceOf; totalSupply counts all | One path updates partitions but not totals |
| Default partition | Written selection rule, tested on transfer and redeem | Transfer and redeem draw partitions in different orders |
| Preflight matches execution | Fuzz test: canTransfer result equals the transfer outcome | View and transfer run different checks |
| Every transfer path | Restriction tests for each transfer, data, partition and operator function | Rules enforced on transfer only |
| Signed data | Schema binding chain, contract, parties, amount, expiry and nonce | One approval works twice, or on another chain |
| Operators | Revocation tests for all-partition and per-partition grants | Revoked operator still moves one partition |
| Issuance | Issuer role holder, per-call cap, isIssuable shutoff tested | Deployer key can issue without limit |
| Controller | Multisig threshold, approval log, alerts on ControllerTransfer events | Controller is a single hot key |
| Documents | setDocument role, hash on every entry, DocumentUpdated alerts | One key can swap the offering document |
| Upgrades | Timelock, storage layout diff, locked initializers | Upgrade can re-enable a disabled controller |
| Deployment | Bytecode and role config matched to the audited commit per chain | Unverified contracts, or roles differ by chain |
ERC-1400 vs ERC-3643
ERC-3643, known as T-REX, is a Final ERC created on July 9, 2021. It builds identity and compliance checks into the standard itself.[7]
Its normal transfers need a verified receiver and compliance approval. Mint and forced transfers bypass the compliance rules, and burn bypasses eligibility checks.
Whichever you pick, those bypass paths need their own authorization tests, exactly like ERC-1644 controller calls.
This guide covers building and auditing ERC-1400. For status, gas and composability side by side, read our ERC-3643 vs ERC-1400 comparison.
Buying a platform rather than building? Use our tokenization platform due diligence checklist instead.
| Question | ERC-1400 | ERC-3643 |
|---|---|---|
| Status | Draft since September 2018 | Final since July 2021 |
| Who is eligible | Your rules behind canTransfer | Onchain identity and compliance interfaces |
| Classes of one asset | Partitions through ERC-1410 | Not defined in the standard's interfaces |
| Forced moves | controllerTransfer, controllerRedeem | Forced transfer, burn and recovery by agents |
| Pause and freeze | Left to the implementation | Defined in the standard |
Audit your ERC-1400 token before issuance
Guardian's smart contract audit puts two independent teams on one scope and fuzzes partition, supply and role invariants across every reachable state. The invariant suite stays with you.
Frequently Asked Questions
Will an ERC-1400 token work with ERC-20 wallets and DeFi?
Wallets and explorers can read balances, because the suite stays ERC-20 compatible. Transfers still revert when your rules say no, so a pool, vault or bridge contract must pass those rules before it can receive the token.[1]
Does ERC-1400 make a token compliant with securities law?
No. The drafts define interfaces and events only. Legal classification, the offering's compliance, the KYC process, custody and each jurisdiction's duties sit outside them, so counsel and your transfer rules must cover those.[1]
Does an ERC-1643 document prove investors received it?
No. An onchain entry shows which file the issuer published and when it last changed, not that any investor opened or accepted it. Keep delivery and acknowledgment records offchain.[4]
Related reading
- erc 3643 vs erc 1400
- rwa tokenization
- tokenization platform due diligence checklist
- erc20 vulnerabilities
- emergency pause design
Sources
- SecurityTokenStandard GitHub: ERC-1400 Security Token Standards
- SecurityTokenStandard GitHub: ERC-1410 Partially Fungible Token Standard
- SecurityTokenStandard GitHub: ERC-1594 Core Security Token Standard
- SecurityTokenStandard GitHub: ERC-1643 Document Management Standard
- SecurityTokenStandard GitHub: ERC-1644 Controller Token Operation Standard
- ConsenSys GitHub: UniversalToken: Implementation of Universal Token for Assets and Payments
- Ethereum Improvement Proposals: ERC-3643: T-REX
- Guardian Security: Circumvented Token Transfer Restrictions (DN404 review)
- Guardian Resource Hub: ERC-3643 vs ERC-1400: Choosing a Security Token Standard
- Guardian Security: Smart contract audit services