ERC-3643 primary sources — 2026-05-08

Project status in this pass

• ERC-3643 is already a finalized EIP and is presented by its ecosystem materials as the core standard behind the T-REX regulated-token stack.
• A standalone T-REX v4 whitepaper exists in official documentation, but this pass relied mainly on the EIP text, Tokeny docs, and the core repository README.
• The materials consistently frame ERC-3643 as a full permissioned-token control system, not just an ERC-20 extension.

Primary-source snapshots

1) Official EIP / abstract and motivation

• URL: https://eips.ethereum.org/EIPS/eip-3643
• Key excerpt/signals:
  • The abstract calls ERC-3643 an institutional-grade security-token standard using automated onchain validation and onchain identities for eligibility checks.
  • The motivation says tokenized securities cannot be permissionless like utility tokens and need ownership tracking plus investor-eligibility enforcement.
  • The specification requires ERC-20 compatibility alongside compliance rules, recovery, freeze, pause, mint/burn, agent roles, forced transfers, and batch actions.
• Why it mattered:
  • This is the clearest source showing that ERC-3643 is an opinionated regulated-market operating stack rather than a narrow transfer-hook standard.

2) Official EIP / transfer-path architecture

• URL: https://eips.ethereum.org/EIPS/eip-3643
• Key excerpt/signals:
  • The transfer path requires enough unfrozen balance, receiver verification in the identity registry, non-frozen sender and receiver wallets, an unpaused token, and a passing compliance check.
  • The EIP separates isVerified holder eligibility from canTransfer global token-compliance rules.
  • The examples mention token-holder caps, country-level limits, and maximum-token-per-investor rules as compliance-contract logic.
• Why it mattered:
  • This separation reveals where control centralizes in practice: not just in the token contract, but in the issuer-selected registries and compliance modules sitting behind it.

3) Tokeny documentation page

• URL: https://docs.tokeny.com/docs/the-erc-3643-token-standard
• Key excerpt/signals:
  • Tokeny says it was the initial creator of the protocol, later open-sourced it, and is now one of the founding members of the ERC3643 association.
  • The docs describe ERC-3643 as an open-source protocol for permissioned tokens on EVM networks with built-in decentralized identity and broad tokenization scope across securities, e-money, and other RWAs.
  • The page links out to the main docs site, association site, GitHub org, audits, and a T-REX v4 whitepaper.
• Why it mattered:
  • This clarifies both stewardship and ecosystem posture: ERC-3643 is no longer only a vendor product page, but it still carries a strong creator-led implementation lineage.

4) Core repository README / component model

• URL: https://raw.githubusercontent.com/ERC-3643/ERC-3643/master/README.md
• Key excerpt/signals:
  • The README describes T-REX as a comprehensive suite of Solidity smart contracts implementing ERC-3643.
  • It lists ONCHAINID, trusted issuers, claim topics, identity registry, compliance contract, and security-token contract as key components.
  • It points to documentation, audits, and a whitepaper rather than presenting the standard as a standalone token primitive.
• Why it mattered:
  • This is strong evidence that ERC-3643 should be analyzed as a stack of coordinated registries and policy modules, with multiple hidden vendor and issuer control points.

5) Ecosystem framing / association and docs hubs

• URLs:
  • https://erc3643.org/
  • https://docs.erc3643.org/
• Key excerpt/signals:
  • Official materials present ERC-3643 as the token standard for RWA tokenization and a maintained ecosystem rather than only a historical EIP.
  • The public hubs reinforce that the standard’s practical life sits in implementation and governance around the stack, not just in the EIP text.
• Why it mattered:
  • This helps distinguish ERC-3643 from many nominally “final” standards that have weak downstream operational reality.

Working conclusion

ERC-3643 is best cataloged as a thick regulated-token control plane. Its decisive features in this pass were the split between eligibility and compliance, the ONCHAINID-plus-registry stack, and the explicit issuer/agent intervention rights around freezing, forced transfers, pausing, and recovery.