ERC-3643 and ONCHAINID
Permissioned tokens that check holder identity on every transfer
Available on enquiry. General availability is planned for Q1 2027. To activate Tokenisation now, speak with [email protected].
ERC-3643, also known as T-REX (Token for Regulated EXchanges), is an Ethereum standard for permissioned tokens, such as tokenised securities. It keeps the ERC-20 interface, so wallets and explorers can read balances, but tokens can only move between holders whose identity has been verified. Tokenisation deploys Tokeny's T-REX implementation.
How a transfer is checked
Every transfer, and every mint, passes two checks before it succeeds:
- Identity. The Identity Registry confirms the recipient's address is linked to an ONCHAINID identity that holds a valid Know Your Customer (KYC) claim from a trusted claim issuer.
- Compliance. The token's compliance contract confirms the transfer meets the rules of its compliance modules.
If either check fails, the transaction reverts and no tokens move.
What a deployment creates
| Component | Role |
|---|---|
| Token | The ERC-3643 token contract. Your vault is its owner and agent. |
| Identity Registry | Links holder addresses to their ONCHAINID identities, and runs the identity check. |
| Claim Topics Registry | Lists the claims holders need. Tokenisation sets this to KYC. |
| Trusted Issuers Registry | Lists the claim issuers you trust. Our claim issuer is trusted by default, and you can add others. |
| Compliance | Holds the token's transfer rules. You attach compliance module contracts by address. |
ONCHAINID
ONCHAINID is an on-chain identity contract for each holder, based on ERC-734 (key management) and ERC-735 (claims). A claim issuer verifies the holder off chain and adds a signed claim to their identity. The token never stores personal data: it only checks that a valid claim exists from an issuer you trust.
Tokenisation can create ONCHAINID identities for holders, with a vault holding the management keys, and add or remove claims on them.
Before you issue an ERC-3643 token, decide:
- How holders complete KYC, and which claim issuers you trust.
- Whether holders bring their own ONCHAINID or you create one for them.
- Which compliance modules the token needs, such as holder limits or country restrictions.
Agent actions
As the token's agent, your vault can:
- Mint and burn, including burning from any holder.
- Pause all transfers.
- Freeze an address, or part of its balance.
- Make a forced transfer between verified holders, for example to execute a court order.
- Register holder identities, and update a holder's identity or country.
- Add, remove, and configure compliance modules.
Each action needs your signers' approval. Recovering a holder's tokens to a new address isn't supported.
ERC-3643's on-chain compliance rules are part of the token. They are separate from the transaction policies in the io.vault Compliance module, which is coming soon.
Updated 17 days ago