Skip to content
Glossary

ERC-3643

ERC-3643 is an Ethereum standard for permissioned security tokens that checks each holder's verified on-chain identity before allowing a transfer, enforcing compliance in the token itself.

ERC-3643 is an Ethereum token standard for permissioned security tokens - tokens that can only be held and transferred by investors who have been verified. Also known as the T-REX standard, it was built specifically for regulated real-world assets, where the issuer must control who owns the token at all times. It is a finalized ERC, maintained by an industry association.

Its defining feature is on-chain identity. Every potential holder is linked to a verified identity (using the ONCHAINID framework), and the token contract checks that identity against a set of compliance rules before any transfer executes. If a buyer is not verified, not on the approved list, or barred by a rule - a jurisdiction block, a holding limit, a lock-up period - the transfer simply reverts. Compliance is enforced by the code, not by a back-office promise.

ERC-3643 extends the ERC-20 model, so balances and transfers look familiar to standard tooling, but it adds the identity registry, the compliance module, and agent roles that let the issuer freeze accounts, force transfers for legal recovery, or recover tokens from a lost wallet. In practice it combines a whitelist with pluggable transfer restrictions.

This matters because a security cannot behave like a permissionless token. A token entitling you to someone's profits usually must stay within a pool of KYC'd, eligible investors, and ERC-3643 bakes that requirement into the asset itself, so it travels with the token across wallets and venues.

The alternative lineage is ERC-1400, an earlier security-token suite. ERC-3643's emphasis on built-in verified identity has made it a common choice for compliant issuance as of 2026.

Source: ERC-3643 Association (erc3643.org), as of 2026.

Mentioned in

  • Whitelisting & Transfer Restrictions in Code

    Whitelisting and transfer restrictions in a security token's code - how the contract checks approved wallets on every transfer to keep a regulated token compliant.

  • ERC-3643 vs ERC-1400: Token Standards

    ERC-3643 vs ERC-1400 - the two leading compliant security-token standards compared on identity, transfer control, and flexibility, and how to choose for your RWA.

  • How to Deploy a Compliant Security Token

    How to deploy a compliant security token step by step - choosing the standard, configuring the whitelist and transfer rules, auditing, and deploying safely.

  • RWA Reference Architecture

    An RWA smart-contract reference architecture - the factory, funding, compliance, and distributor contracts that make up a production tokenization stack.

  • RWA Smart Contracts & Tech Stack

    The RWA tokenization tech stack - compliant token standards, whitelisting, oracles, audits, and the contract architecture that connects a token to a real asset.

  • What Is Wallet Whitelisting & KYC?

    What is wallet whitelisting and KYC? How tokenized securities restrict holding to approved, identity-verified wallets - and why the rule is built into the token.

Educational content, not financial or legal advice.