Skip to content
Basis Desk
RWA & Tokenization · 7 min read Last reviewed November 20, 2026

ERC-3643 and Permissioned RWA Standards, Explained

Tokenized real-world assets demand compliance at the smart contract level. The ERC-3643 standard, built on the T-REX framework, uses decentralized identity registries to enforce automated transfer restrictions.

Editorial oversight: Julian Mercer, Chief Editor
Neutral
ERC-3643 and Permissioned RWA Standards, Explained

Key points

  • ERC-3643 is an open Ethereum standard that uses smart contracts to enforce regulatory compliance for tokenized securities.
  • The ONCHAINID framework binds wallet addresses to decentralized identities containing cryptographic claims, keeping private PII off the blockchain.
  • Every transaction executes a conditional check via a Compliance Engine, automatically rejecting transfers to unverified or unauthorized wallets.
  • The standard includes native asset recovery functions, allowing issuers to reissue tokens if an investor loses their private keys or faces court actions.

Traditional financial assets require identity verification, regulatory clearances, and geographic restrictions before they change hands. Standard cryptocurrency tokens, by contrast, prioritize permissionless execution, allowing any wallet to send balances to any other wallet without intermediaries. The ERC-3643 standard bridges this divide by embedding automated compliance controls directly into Ethereum smart contracts, enabling institutions to tokenize securities while adhering to securities regulations.

Originally developed under the name T-REX (Token for Regulated EXchanges), ERC-3643 establishes an open protocol for permissioned tokens. Unlike conventional tokens that execute transfers purely based on cryptographic signatures and token balances, ERC-3643 evaluates identity registries, qualification claims, and rule compliance engines before any ledger balance updates.

Why Standard Token Formats Fail for Securities

Public blockchains operate primarily on permissionless accounting models. As detailed in our breakdown of Ethereum token standards like ERC-20, ERC-721, and ERC-1155, an ERC-20 contract executes a transfer if the sender possesses sufficient balance and authorizes the transaction. The smart contract does not inspect the citizenship, accreditation status, or sanctions standing of the recipient address.

Financial regulators—including the Securities and Exchange Commission (SEC) in the United States, the European Securities and Markets Authority (ESMA) in the European Union, and the Financial Conduct Authority (FCA) in the United Kingdom—require issuers of private placements, corporate bonds, and real estate equity to verify purchaser identities. Issuers must prevent unlawful secondary transfers to non-accredited individuals or sanctioned jurisdictions. If a regulated security exists as a standard ERC-20 token on a public network, an investor could transfer that asset to an anonymous wallet in an embargoed country, creating non-compliance liabilities for the issuer.

ERC-3643 solves this problem without compromising blockchain settlement finality. Instead of storing tokens in walled centralized databases or custodial accounts, issuers retain programmatic control over individual token transfers on public networks.

The Architecture of ERC-3643 and ONCHAINID

The ERC-3643 framework decouples investor identification from individual wallet addresses. This separation is handled through four core architectural components: the token contract, the identity registry, the claim topics registry, and the compliance engine.

The foundation of investor eligibility is ONCHAINID, a decentralized identity system built on top of the ERC-734 and ERC-735 identity standards. Under this architecture, each participant in an asset's lifecycle deploys an individual smart contract that serves as their digital identity. This contract does not store raw personally identifiable information (PII) such as passports, home addresses, or tax identification numbers. Storing sensitive data on a public ledger creates severe data protection risks under regulations such as the General Data Protection Regulation (GDPR) in the European Union.

Instead, trusted qualification authorities deploy cryptographic assertions, known as claims, directly to the investor's identity contract. A claim functions as a digital signature verifying that the owner meets specific criteria, such as passing Know Your Customer (KYC) reviews, residing in an eligible country, or qualifying as an accredited investor.

The Identity Registry contract links an investor's public wallet address to their ONCHAINID contract. When an issuer creates a tokenized security using ERC-3643, the token references this Identity Registry. The token contract does not evaluate raw user documents; it queries the registry to determine whether a valid identity contract exists for the target wallet and whether an authorized third party has attested to the required claims.

How Transfer Approvals Work in Practice

Every time a transfer is initiated under ERC-3643, the smart contract executes a conditional pre-flight check before adjusting balances. This check is governed by a dedicated Compliance Engine contract.

When address A attempts to transfer an asset to address B, the token invokes an internal check function: canTransfer(address _from, address _to, uint256 _amount). The function evaluates two distinct operational layers: user eligibility and asset-level compliance rules.

First, the Identity Registry verifies that both address A and address B are bound to valid ONCHAINID contracts. Next, it verifies that both identities contain valid claims from approved issuers. If the token requires claims for Topic 1 (KYC/AML approval) and Topic 2 (Accredited Investor status), the transfer immediately reverts if either party lacks those cryptographic attestations.

Second, the Compliance Engine evaluates programmatic market rules established by the token issuer. These rules might limit the maximum number of legal shareholders residing in a specific country, cap the percentage of supply a single investor can accumulate, or enforce minimum holding lock-up periods. If both conditions pass, the contract processes the transfer. If either fails, the transaction reverts, consuming network execution gas but leaving the token balances unchanged.

A Worked Example: Cross-Border Equity Settlement

To understand how these components interact, consider a tokenized commercial real estate debt offering issued under US Regulation D (Rule 506(c)) and Regulation S.

Assume the issuer establishes the following conditions:

  • Identity requirements: Must hold Claim 101 (KYC verified by an approved agency) and Claim 102 (Accredited Investor certification).
  • Compliance Engine limits: A mandatory 365-day holding lock-up for secondary transfers between US citizens, and a cap of 2,000 maximum non-accredited European participants under cross-border rules.

Investor Alice purchases 10,000 tokens of the offering on Day 1. Alice completes identity verification through a certified compliance provider, who writes a cryptographic signature corresponding to Claim 101 and Claim 102 to Alice's ONCHAINID. Alice's primary Ethereum wallet is registered to her ONCHAINID in the token's Identity Registry.

Six months later (Day 182), Alice initiates an on-chain transaction to transfer 5,000 tokens to Bob. Bob is also a US citizen who has completed KYC verification and holds Claim 101 and Claim 102 in his ONCHAINID.

When the token contract processes Alice's transaction, it queries the Identity Registry. Both Alice and Bob are confirmed as verified participants. However, when the token calls the Compliance Engine, the engine inspects the asset-level rules. Because the holding period between US investors is set to 365 days, and only 182 days have elapsed since Alice's initial acquisition, the transaction fails. The smart contract triggers an execution revert, outputting an error code indicating a rule lock-up violation.

On Day 366, Alice attempts the identical transaction. The contract queries the Identity Registry, verifies that Alice and Bob remain valid claim holders, confirms that the 365-day lock-up timer has expired, and permits the balance transfer. Bob receives the 5,000 tokens on-chain without the issuer manually reviewing the settlement.

Real-world securities regulations require issuers to maintain mechanisms for legal intervention. If an investor loses their private keys, becomes subject to an asset forfeiture order from a court, or is placed on an active international sanctions list, the issuer must have the technical capability to intervene.

Permissionless formats do not allow third-party intervention; losing a private key permanently locks the underlying tokens. ERC-3643 addresses this requirement through role-based recovery and freeze functions assigned to the issuer or designated compliance agents.

If an investor establishes through external legal procedures that their wallet key has been compromised, the issuer can call the contract's recovery module. The smart contract invalidates the old wallet address in the Identity Registry, binds the investor's verified ONCHAINID to a newly generated wallet address, burns the tokens at the compromised address, and mints an equivalent balance to the replacement wallet. Because all identity assertions and historical records remain intact within the ONCHAINID contract, the investor's transaction history and legal entitlement are preserved.

Similarly, if an authority issues a freezing order, an issuer can pause transfers for an individual wallet without freezing the entire token contract. Standard ERC-20 implementations that support freezing (such as major centralized stablecoins) typically rely on an internal address blacklist. ERC-3643 standardizes these intervention mechanics across all compliant security tokens, establishing an auditable ledger trail for regulatory filings.

Common Misconceptions

ERC-3643 compromises investor privacy on public ledgers

A common assumption is that permissioned standards publish sensitive identification data to public blocks. In practice, the ONCHAINID architecture stores no personally identifiable information on the blockchain. The ledger stores only cryptographic hashes and digital signatures issued by trusted compliance entities. External observers can see that an address holds an accreditation assertion from a recognized verification agency, but they cannot read the investor's name, financial statements, or residential address.

Permissioned tokens run only on private blockchains

While ERC-3643 can be deployed on private or consortium networks, it is optimized for deployment on public networks such as Ethereum. Because the compliance checks are hardcoded into the contract, the asset remains compliant even in public environments. An unauthorized address cannot purchase, receive, or interact with the token balances, eliminating the operational need to restrict the network layer itself.

The standard relies on manual transaction approval

ERC-3643 is not a multi-signature escrow protocol where an issuer must sign off on every individual trade. The administrative burden is shifted to onboarding: once an investor is verified and registered, secondary transactions execute autonomously. The Compliance Engine checks mathematical conditions in real time, enabling atomic peer-to-peer settlement without human intervention.

How This Connects to the Market

As the tokenization of private credit, government debt, and structured real estate moves from early experimental pilots into institutional settlement infrastructure, standardized permissioning layers are displacing ad-hoc, proprietary solutions. In December 2023, ERC-3643 achieved formal adoption as an accepted Ethereum Improvement Proposal (EIP), signaling standard consensus for regulated asset issuance across the EVM ecosystem.

Institutional capital allocators operating within European jurisdictions under the Markets in Crypto-Assets (MiCA) framework or the EU DLT Pilot Regime require legal certainty that securities laws apply equally on-chain. Market operators in the US face parallel obligations under Financial Industry Regulatory Authority (FINRA) and SEC mandates. By delegating compliance verification to self-sovereign identity contracts while enforcing trading boundaries inside bytecode, ERC-3643 provides an institutional on-ramp that maintains compatibility with public smart contract architecture.

Questions this story raises

What is the difference between ERC-20 and ERC-3643?
ERC-20 permits token transfers between any two addresses provided the sender has a sufficient balance and pays gas fees. ERC-3643 overrides this behavior by querying an Identity Registry and a Compliance Engine before any transfer executes, blocking transactions if either party lacks valid identity claims or violates offering rules.
Does ERC-3643 store user identity documents on-chain?
No. The ONCHAINID standard relies on cryptographic claims and digital signatures written by verified third-party issuers. Personal identifiable information (PII) remains off-chain with the verifying institution, satisfying data protection standards like GDPR.
Can an issuer freeze or recover ERC-3643 tokens?
Yes. ERC-3643 contains administrative modules that allow authorized agents to freeze transfers for specific non-compliant wallets or burn and reissue tokens to an investor who has lost access to their private keys.
Can ERC-3643 tokens interact with decentralized finance (DeFi) protocols?
Yes, provided the DeFi liquidity pool or automated market maker (AMM) contract is registered in the Identity Registry and meets the compliance criteria defined in the token's Compliance Engine.

References

  1. [1] Guidelines on the DLT Pilot Regime — European Securities and Markets Authority
  2. [2] Understanding the Regulation of Tokenized Securities — Securities and Exchange Commission
  3. [3] EIP-3643: T-REX - Token for Regulated EXchanges — Ethereum Improvement Proposals
  4. [4] ERC-3643 Official Protocol Documentation — ERC-3643 Association

Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.