What is ERC-3643 and how does it restrict transfers?

It is a permissioned token standard. Before any transfer, the token asks its identity registry whether the receiving wallet belongs to a verified investor with the required claims, and asks its compliance contract whether the transfer fits the offering's rules. If either says no, the transfer fails. Agents of the issuer can also freeze wallets, force transfers and recover lost wallets.

What contracts make up an ERC-3643 token?

The token itself; an identity registry that maps wallets to on-chain identity contracts and countries (with separate storage so several tokens can share it); a trusted issuers registry listing who may issue claims; a claim topics registry listing which claims are required, such as KYC or accreditation; and a modular compliance contract holding the offering's rules. Investors' identities are on-chain identity contracts that hold signed claims.

Is an ERC-3643 token the same as an ERC-20 token with a whitelist?

It is compatible with ERC-20 but more structured. Identity, trusted claim issuers, required claim types and compliance rules are separate, replaceable components, and the agent functions for freezing, forced transfers and recovery are part of the standard rather than custom code.

Does using ERC-3643 make a token compliant?

No. It enforces the rules the issuer configures; it does not choose them. The offering exemption, disclosures, the legal rights the token represents, which record controls ownership, and who holds the agent keys are all decided outside the standard.

ERC-3643 Standard

Tokenized Real-World Assets

Definition

ERC-3643 is a token standard for Ethereum and compatible blockchains designed for securities and other regulated assets. It originated as the T-REX protocol and is maintained with the ERC-3643 Association. An ERC-3643 token behaves like an ordinary ERC-20 token for balances and transfers, but every transfer must pass two checks before it executes: the receiving wallet must be verified in an identity registry, which links wallets to on-chain identities carrying claims such as KYC completion, investor status and country issued by trusted parties; and a modular compliance contract must confirm the transfer does not break offering rules, such as investor caps, country restrictions or holding limits. The standard also gives the issuer's agents functions to mint and burn, pause the token, freeze whole wallets or specific amounts, force transfers and recover lost wallets. It encodes transfer restrictions; it does not decide what the token represents, which record is the legal register, or whether the offering complies with securities law.

Why it matters

Securities cannot move to anyone, anywhere, at any time: offering exemptions limit who may hold them, fund structures cap investor counts, and sanctions and court orders must be enforced. ERC-3643 is one standardized way to make a token respect those limits on-chain, and it makes the issuer's controls explicit and inspectable rather than buried in custom code. That cuts both ways for investors. It means an ERC-3643 token will refuse transfers to ineligible wallets and can recover lost holdings. It also means the issuer's agents can freeze and move tokens, and the token's behavior depends on who maintains the identity registry and the compliance rules. Whether a product uses ERC-3643 or a comparable permissioned design, the same questions apply: who verifies identities, who sets the rules, who holds the agent keys, and which record governs ownership.

Common misconceptions

•ERC-3643 does not make a token legal. The offering still needs a valid exemption or registration, disclosures and a compliance program.
•Permissioned transfers do not remove operational risk. Identity providers, claim issuers, transfer agents and agent keys become critical dependencies.
•It is not just ERC-20 with a whitelist. Identity, claims and compliance are separate components with defined roles.
•On-chain transferability does not mean liquidity. Eligible buyers, venues and issuer processes still limit trading.
•The token is not necessarily the legal register. The documents decide whether the chain or an off-chain record controls.

Technical details

The components

Token: ERC-20-compatible balances and transfers, with transfer hooks that call the checks below.

Identity registry and its storage: link each wallet to an on-chain identity contract and a country code.

Trusted issuers registry: the parties allowed to sign claims, such as a KYC provider or the transfer agent.

Claim topics registry: the claims a holder must have, such as identity verified or accredited investor.

Modular compliance: the offering's rules as modules, such as maximum holders, country limits, holding caps or lock-ups.

A transfer, step by step

The holder calls transfer to send 1,000 tokens to another wallet.

The token checks the sender is not frozen and has at least 1,000 unfrozen tokens.

The identity registry checks the receiver's wallet is linked to an identity with valid claims for every required topic, signed by trusted issuers.

The compliance contract checks the transfer against each module, for example that the receiver's country is permitted and the holder count stays under the cap.

If every check passes, balances update and compliance state is recorded; if any fails, the transfer reverts and nothing moves.

Agent functions

mint and burn: issue and cancel tokens for subscriptions, redemptions and corrections.

pause and unpause: halt and resume all transfers.

setAddressFrozen, freezePartialTokens and unfreezePartialTokens: whole-wallet and partial freezes.

forcedTransfer: move tokens without the sender's signature, to a verified receiver.

recoveryAddress: move a lost wallet's balance to a new wallet registered to the same identity; batch versions exist for most functions.

What the standard leaves to the issuer and documents

The legal instrument: equity, debt, fund interest or a beneficial interest.

The offering basis: Regulation D, Regulation S, Regulation A or registration, which sets who may hold.

The authoritative record: the chain, or the transfer agent's off-chain register.

Key governance: who holds owner and agent roles, with what approvals and notice.

Upgradeability: whether the contracts can be replaced, and by whom.

How investors apply the term

Investors usually apply this term by tying the definition back to the controlling documents and then asking which cash flows, rights, restrictions, or valuation assumptions it changes. A useful review looks at the term alongside fees, leverage, liquidity, reporting frequency, and manager discretion rather than treating it as a standalone concept.

The practical diligence test is simple: identify who benefits if the assumption is wrong, who has control when conditions change, and what evidence the investor receives after closing. Terms that cannot be reconciled to documents, cash movements, and monitoring data should be treated as marketing shorthand until proven otherwise.

Frequently asked questions

What is ERC-3643 and how does it restrict transfers?: It is a permissioned token standard. Before any transfer, the token asks its identity registry whether the receiving wallet belongs to a verified investor with the required claims, and asks its compliance contract whether the transfer fits the offering's rules. If either says no, the transfer fails. Agents of the issuer can also freeze wallets, force transfers and recover lost wallets.
What contracts make up an ERC-3643 token?: The token itself; an identity registry that maps wallets to on-chain identity contracts and countries (with separate storage so several tokens can share it); a trusted issuers registry listing who may issue claims; a claim topics registry listing which claims are required, such as KYC or accreditation; and a modular compliance contract holding the offering's rules. Investors' identities are on-chain identity contracts that hold signed claims.
Is an ERC-3643 token the same as an ERC-20 token with a whitelist?: It is compatible with ERC-20 but more structured. Identity, trusted claim issuers, required claim types and compliance rules are separate, replaceable components, and the agent functions for freezing, forced transfers and recovery are part of the standard rather than custom code.
Does using ERC-3643 make a token compliant?: No. It enforces the rules the issuer configures; it does not choose them. The offering exemption, disclosures, the legal rights the token represents, which record controls ownership, and who holds the agent keys are all decided outside the standard.