The ERC-3643 security token standard — also called T-REX, short for Token for Regulated EXchanges — is the Ethereum community’s finalized answer to a straightforward problem: how do you issue a regulated security on a public blockchain without letting any wallet in the world hold it?
A plain ERC-20 token moves wherever its holder points it. That is fine for a utility token or a stablecoin, but securities law requires something different: ownership must be tracked, transfer restrictions must be enforced, and the issuer must retain a last-resort ability to act when a court orders it or an investor loses their keys. ERC-3643 builds all of that into the token contract itself, so the rules apply on every transfer — not just at the moment of initial distribution.
This article explains how the standard works, what its key components do, how it compares with ERC-20 and ERC-1400, and why it has become the reference point for regulated RWA tokenization on EVM chains.
From Draft to Final: ERC-3643’s Official Status
The T-REX protocol was first proposed as an Ethereum Improvement Proposal in 2021. After two years of review, the ERC-3643 standard reached Final status in its EIP on 15 December 2023, making it the first standard tailored specifically for compliant tokenization to earn that recognition from the Ethereum community. Final status means the specification has been formally reviewed, discussed and agreed upon — the same rigorous process that produced ERC-20 and ERC-721.
The ERC-3643 Association, a non-profit with institutional members including asset managers, law firms and infrastructure providers, now stewards the standard. The European Securities and Markets Authority (ESMA) has also referenced ERC-3643 in its report on the DLT Pilot Regime as an example of a standard capable of enforcing compliance for tokenized securities.
The Four-Layer Architecture
ERC-3643 is not a single smart contract — it is a coordinated suite of contracts that together implement four distinct functions:
- ONCHAINID (identity layer). Every participant — investor, issuer, or intermediary — is assigned an on-chain identity contract built on the ERC-734 and ERC-735 standards for key management and verifiable claims. ONCHAINID is portable: an investor verified once can hold tokens issued by multiple issuers without undergoing a fresh KYC process for each one.
- Identity Registry. The token maintains a registry of ONCHAINID addresses that are permitted to hold it. Before a transfer completes, the registry confirms that the recipient’s wallet is linked to a registered, verified ONCHAINID.
- Trusted Issuers Registry. Not every claim on an ONCHAINID is accepted — only claims signed by issuers the token recognises as trusted (a licensed KYC provider, for example) are considered valid. This registry lists those trusted claim issuers.
- Compliance Contract (modular rules engine). A separate contract encodes the offering’s specific business rules and consults them on every transfer. Rules are written as independent, swappable modules, so the issuer can update them without redeploying the token.
How Every Transfer Is Checked
When a holder initiates a transfer, the token contract runs two sequential checks before the balance actually moves:
isVerified()— who is receiving? The recipient’s wallet must be linked to an ONCHAINID that holds the claims the token requires (such as a completed KYC check or an accredited-investor attestation) from a verifier the Trusted Issuers Registry recognises.canTransfer()— do the rules allow it? The Compliance contract checks the transfer against the offering’s programmed rules.
If either check fails, the transaction reverts automatically. No intermediary needs to intervene; the enforcement is self-executing at the smart-contract level.
Compliance modules can encode virtually any offering rule, including:
- Maximum number of holders per jurisdiction
- Position-size limits per investor
- Jurisdiction allow or deny lists
- Lock-up periods and vesting schedules
- Minimum holding periods after primary issuance
Because modules are separate contracts plugged into the Compliance contract, rules are added or changed without redeploying the token itself, keeping the token’s on-chain history intact.
Forced Transfers, Freezes and Wallet Recovery
Regulated securities are subject to scenarios that permissionless blockchains were not designed for: court-ordered seizures, fraud remediation, and investors who lose access to their private keys. ERC-3643 addresses all three through an explicit Agent role.
The standard defines an Agent role appointed by the token’s owner (the issuer). Agents can:
- Force a transfer — move tokens from one wallet to another without the holder’s signature, for example to enforce a court order. The receiving wallet must still pass
isVerified(). - Freeze a wallet — fully or partially restrict an address from sending or receiving tokens.
- Pause the token — halt all transfers globally.
- Recover a lost wallet — reissue the economic position of an inaccessible wallet to a new, verified address via
recoveryAddress(), preserving the cap-table history rather than erasing it.
All of these actions emit on-chain events, creating an immutable audit trail — a property that transfer agents and compliance officers in traditional finance expect as standard. Because agent powers are substantial, production deployments typically protect the agent role behind a multi-signature wallet or governance contract.
ERC-3643 vs. ERC-20 and ERC-1400
Three standards dominate the conversation for tokenized securities, and each occupies a different point on the compliance spectrum.
ERC-20 is the foundation. It defines the familiar transfer, approve and transferFrom functions and checks only that the sender has a sufficient balance. It has no concept of who holds the token, no transfer restrictions and no issuer controls. That makes it ideal for utility tokens and stablecoins — and unsuitable on its own for a regulated security.
ERC-1400 is an earlier security-token framework proposed in 2018. It introduced useful concepts: partitions (or tranches) for modelling different share classes, a canTransfer pre-check returning a reason code, and controller operations for forced transfers (via ERC-1644). However, ERC-1400 never moved past Draft status and was never finalized as an official Ethereum ERC. It leaves identity and compliance implementation entirely to each issuer, which fragments interoperability across deployments. For assets with multiple share classes or complex tranched structures, ERC-1400 is still a reasonable design reference — but the momentum and standardisation have shifted.
ERC-3643 sits at the most opinionated end of that spectrum. It is ERC-20-compatible (any wallet or protocol that accepts ERC-20 tokens accepts ERC-3643 tokens without modification), carries Final ERC status, and builds identity and compliance directly into the standard rather than leaving them to each implementer. The trade-off is higher gas cost and architectural complexity compared with a plain ERC-20 — a reasonable price for an instrument that must satisfy securities regulators.
| ERC-20 | ERC-1400 | ERC-3643 (T-REX) | |
|---|---|---|---|
| Standard status | Final ERC | Draft (never finalized) | Final ERC |
| Transfer restriction | None | canTransfer (reason code) | isVerified + canTransfer (must pass both) |
| On-chain identity | None | Custom per issuer | ONCHAINID (standardised) |
| Compliance modules | None | Custom per issuer | Pluggable, swappable modules |
| Issuer controls | None | Controller transfers (ERC-1644) | Forced transfer, recovery, freeze, pause |
| ERC-20 compatibility | Native | Requires adapter contracts | Native |
Why Regulated Issuers Prefer ERC-3643
Five properties make ERC-3643 the natural choice for issuers who cannot afford compliance gaps:
- Automatic enforcement. Compliance logic lives in the token itself, so a non-compliant transfer is impossible — not merely prohibited by policy.
- Portable investor identity. An investor’s ONCHAINID travels with them. Once verified by a trusted claim issuer, they can hold tokens from multiple issuers without repeating the KYC process — reducing friction for investors and cost for issuers.
- Regulator-readable audit trail. Every transfer, freeze, forced transfer and recovery is recorded on-chain, giving compliance officers and regulators a single, tamper-proof source of truth.
- Upgradeability without token migration. New compliance rules are deployed as fresh modules and plugged in; the token contract and its cap-table history remain unchanged.
- Official recognition. Final ERC status and ESMA’s reference to the standard in its DLT Pilot Regime report signal to institutional counterparties that ERC-3643 is not a proprietary implementation — it is an open, community-ratified specification.
ERC-3643 on the Libertum Platform
Libertum’s T-Suite natively supports ERC-3643 as one of its core token standards on EVM chains — alongside ERC-20 and ERC-721, as well as CIP-113 on Cardano and XRPL issued currencies and Multi-Purpose Tokens. When an issuer deploys a security token through T-Suite’s Tokenization Wizard, they can select ERC-3643 and benefit from the full architecture described above: identity registry, trusted-issuer configuration, pluggable compliance modules, and agent-controlled forced transfers and recovery.
The T-Suite user manual covers how each supported standard is implemented on the platform, and the compliance documentation walks through how compliance modules are configured for a specific offering. For issuers who need help preparing the offering documents before token deployment, Libertum’s Structuring tool helps draft counsel-ready documentation — it is software, not legal advice.
If you are evaluating whether ERC-3643 is the right standard for your tokenization project, explore the platform or speak to the team.
FAQ
What is ERC-3643 and why is it called T-REX?
ERC-3643 is a Final-status Ethereum token standard for permissioned, compliance-enforcing tokens. T-REX stands for Token for Regulated EXchanges and was the original name of Tokeny’s reference implementation before the protocol was submitted to the Ethereum Improvement Proposal process and ratified by the community in December 2023.
Can an ERC-3643 token be transferred to any Ethereum wallet?
No. Before a transfer completes, the token checks that the recipient’s wallet is linked to an ONCHAINID that holds the required claims (such as a valid KYC attestation) from a trusted issuer, and that the transfer passes the offering’s compliance rules. If either check fails, the transaction is automatically rejected on-chain.
How does ERC-3643 compare with ERC-1400 for a new issuance?
ERC-1400 introduced useful concepts — partitions, pre-transfer checks, controller operations — but it was never finalized as an official Ethereum ERC and leaves identity and compliance implementation to each issuer. ERC-3643 is a Final ERC with a standardised on-chain identity layer (ONCHAINID) and modular compliance built into the specification. For a single-class regulated token where automated identity-based compliance is the priority, ERC-3643 is generally the cleaner choice; ERC-1400 retains relevance for complex cap structures with multiple tranches or share classes.