Why ERC-3643 for real-world assets
Tokenized securities and RWAs cannot behave like free ERC-20s. Issuers must identify stakeholders and enforce transfer restrictions. ERC-3643 (T-REX) keeps Ethereum permissionless while permissioning the token: every transfer checks Identity Registry eligibility and Modular Compliance rules.
- ERC-20 compatible interface for wallets and explorers
- OnchainID stores keys and claims for investors
- Claim Topics + Trusted Issuers encode KYC/AML attestations
- Agents can mint, freeze, pause, and recover when policy requires
Bootstrap infrastructure once per chain
Implementations, OnchainID Factory, TREXImplementationAuthority, and TREXFactory are shared infrastructure. Ethereum Toolset walks you through this wallet flow once, then saves the factory address locally so later issuances are a single deployTREXSuite transaction.
Issue the suite and onboard investors
Provide name, symbol, decimals, owner/agents, and a unique CREATE2 salt. After the suite deploys, create an OnchainID for each investor, registerIdentity on the IR (with ISO country code), then mint as a token agent. Optional KYC claim topics can be registered at issuance — you still need ClaimIssuer signatures for claim-gated eligibility.
When to use ERC-20 instead
Utility tokens, community points, and experiments without investor eligibility checks should use the OpenZeppelin ERC-20 Token Creator. Use ERC-3643 when permissioned transfers and identifiable holders are mandatory.