Final ERC standard. T-REX (Token for Regulated EXchanges) is an institutional-grade permissioned-token framework: every transfer is gated by an on-chain identity registry and a pluggable compliance module, so issuers can enforce KYC, jurisdiction limits, holding periods, and whitelists for security tokens.
- 01tokenized securities and equities
- 02regulated RWA issuance
- 03permissioned stablecoins / fund shares
- 04tokenized funds with KYC'd LP whitelists
- 05any token that needs on-chain compliance enforcement
- pnpm add @tokenysolutions/t-rex
Use the Tokeny `t-rex` reference implementation (`@tokenysolutions/t-rex`, GitHub: `TokenySolutions/T-REX`). The architecture has four pillars: (1) `IToken` — the ERC-20-compatible token, but every `transfer`/`mint` calls `compliance.canTransfer` first; (2) `IIdentityRegistry` — maps wallet addresses to ONCHAINID identity contracts and country codes; (3) `IClaimTopicsRegistry` + `ITrustedIssuersRegistry` — declare which credential claims (KYC, accreditation) are required and which issuers are trusted to sign them; (4) `IModularCompliance` — pluggable rule modules (max holders, country caps, transfer-window, holding-period). Deploy via the T-REX `TREXFactory` for a vetted constellation of contracts. Wire ONCHAINID (ERC-734/735) for the identity layer. The token reverts non-compliant transfers — clients should pre-flight via `canTransfer(from, to, amount)` before signing.
- ⚑Every transfer pays for an external `canTransfer` call plus identity lookups — gas is multiples of a vanilla ERC-20. Batch operations and L2s are strongly recommended.
- ⚑Identity is keyed to a wallet address — losing the wallet without an updated identity registry entry can permanently freeze an investor's holdings. Recovery flows (`recoveryAddress`) must be designed up-front.
- ⚑Compliance module composition order matters — modules are evaluated in sequence and any one rejection blocks the transfer. Misordering can produce false rejections under edge cases like forced transfers.
- ⚑Forced transfers (issuer-initiated) bypass holder consent — necessary for regulatory recovery but a powerful centralization vector. Audit who holds the agent role.
- ⚑Cross-chain: T-REX tokens generally cannot be bridged via standard bridges — the destination chain has no identity registry. Use issuer-controlled bridge or wrapped-only secondary markets.
- ⚑Pausable + freezable: tokens can be globally paused and individual addresses frozen by an agent role. UI must surface this clearly to holders.