ERC-3643 (T-REX: Token for Regulated Exchanges)

ERC-20 vs ERC-3643 technical differences are fundamental to understanding RWA token design. ERC-20 (ordinary token standard, like USDC, USDT): transfer() function logic: deduct X tokens from address A, add X tokens to address B. Only verifies sender has sufficient balance, no recipient qualification verification; any Ethereum address can hold and receive ERC-20 tokens; completely permissionless — no smart contract-level restriction on 'who can hold.' ERC-3643 (compliant token standard, like OUSG, BENJI): transfer() function logic: deduct X tokens from address A → query Identity Registry contract to confirm address B's qualifications → if address B is whitelisted and meets qualification requirements, add X tokens to address B; if address B isn't whitelisted, transaction reverts (fails). Only addresses that have completed KYC in Securitize's system and been added to the whitelist can receive tokens. This technical difference makes ERC-3643 tokens fundamentally 'permissioned tokens' rather than 'permissionless tokens' — the essential dividing line between RWA and DeFi.

ERC-3643's modular design lets issuers flexibly configure compliance rules without rewriting entire contracts. ERC-3643's core components: Token Contract (contains balance mapping, transfer function, and compliance hooks); Identity Registry (maintains 'approved address → investor compliance attributes' mapping — country, qualification level, KYC status); Compliance Contract (defines transfer rules — like: no US addresses can hold Reg S tokens; daily holding limits; pre-transfer lockup periods); Trusted Issuers Registry (which KYC service providers' verification results are accepted by this contract). Practical significance of modular design: Ondo Finance can update compliance rules (like reducing minimum holding from $100K to $50K) without modifying the OUSG token contract itself; in emergencies (like OFAC sanctioning new addresses), can quickly remove specific addresses from whitelist without freezing all tokens.

Ondo Finance choosing ERC-3643 over ERC-20 involves several key considerations that clarify RWA token design trade-offs. Reg D/Reg S technical enforcement needs: OUSG's Reg D exemption requires only 'accredited investors' can hold; Reg S exemption requires tokens not flowing to US markets. These legal requirements must have corresponding technical control mechanisms — ERC-3643's whitelist system makes these legal requirements 'technically enforced rules' rather than 'behavioral norms relying on manual monitoring.' Issuer liability reduction: if OUSG used ordinary ERC-20, Alice could send tokens to any address — including non-KYC addresses, US persons, even sanctioned addresses. Ondo Finance would face compliance liability (allowing non-compliant persons to hold Reg D-exempt securities). ERC-3643 makes these situations technically impossible, substantially reducing issuer compliance liability. Institutional trust building: institutional investors (MakerDAO, pension funds) require verifiable compliance mechanisms in tokenized assets. ERC-3643's whitelist system provides technical guarantee that 'tokens only circulate among compliant investors,' making institutions more willing to allocate OUSG.

ERC-3643's global adoption status and future evolution. Current adoption (mid-2026): Ondo Finance (OUSG, USDY); Franklin Templeton (BENJI's Polygon version); Tokeny Solutions (ERC-3643's primary developer and promoter, having deployed dozens of institutional RWA tokens); some EU tokenized equity programs (leveraging ERC-3643's compliant features to satisfy MiCA's permissioned token requirements). Competitive landscape with other standards: outside Ethereum, different chains have different compliance token standards — Stellar has its own compliance controls (BENJI's Stellar version uses Stellar-native compliance); Solana's compliance tokens (Ondo's USDY on Solana uses Token Extensions). On Ondo Chain (planned), compliance controls will be integrated into the consensus layer rather than application-layer contracts — potentially making Ondo Chain tokens natively compliant without needing application-layer standards like ERC-3643. Evolution direction: as RWA × DeFi integration deepens, ERC-3643's whitelist coverage needs expansion — more DeFi protocols whitelisted, allowing OUSG and similar tokens to be used across broader DeFi ecosystems while maintaining compliance.