A token standard is a technical specification that defines how a digital asset behaves: how it is created, transferred, held, and what events it responds to. For regulated tokenized securities, the choice of token standard is not a minor technical decision — it determines what compliance controls can be enforced, what DeFi protocols the token can interact with, what custody infrastructure can hold it, and whether it will be supported by the institutional infrastructure ecosystem five years from now. ERC-3643 has emerged as the answer to most of these questions for institutional tokenized securities — but understanding why it dominates, what its current limitations are, and how the standard is evolving is essential for institutional participants making long-term infrastructure commitments.
ERC-3643: How It Became the Institutional Default
The Architecture
ERC-3643 extends Ethereum’s ERC-20 standard (the universal token framework) with a mandatory compliance layer. In a standard ERC-20 token, any wallet can receive a transfer: the contract simply checks that the sender has sufficient balance. In an ERC-3643 token, every transfer is checked against an identity registry before execution: the recipient wallet must be associated with a verified ONCHAINID identity that satisfies the token’s compliance requirements (jurisdiction eligibility, KYB/KYC verification status, investor classification). Transfers that fail the compliance check are automatically rejected at the smart contract level — not by a post-trade compliance review, but by the transfer mechanism itself.
The Reference Implementation: T-REX Protocol
The T-REX (Token for Regulated Exchanges) protocol is Tokeny’s open-source reference implementation of ERC-3643. It provides a complete set of audited smart contracts — the token contract, the identity registry, the compliance module, the trusted issuers registry — that any institution can deploy as a base layer for regulated tokenized securities issuance. T-REX has been used to tokenize over $32 billion in real-world assets across more than 180 jurisdictions, making it the most deployed regulated tokenization framework in the world.
Regulatory Validation
The SEC Chairman’s citation of ERC-3643 by name in a July 2025 speech is the highest-profile regulatory endorsement that any specific blockchain token standard has received. The fact that the SEC’s leadership is engaging with the technical details of token standards at this level confirms that ERC-3643 has moved from developer experiment to regulatory attention. DTCC’s ComposerX tokenization pilot is built on ERC-3643. MAS Singapore’s Project Guardian is built on ERC-3643. BX Digital (Börse Stuttgart Group) uses ERC-3643 for regulated digital securities. 21X, the EU-regulated digital exchange, is built entirely on ERC-3643. ISO standardisation is underway.
What Is Happening Beyond the Core Standard
Hedera Integration: Multi-Chain Reach
In December 2025, Hedera integrated ERC-3643 into its Asset Tokenization Studio — an open-source toolkit for configuring, issuing, and managing tokenized bonds and equities on the Hedera network. The integration brings ERC-3643’s compliance architecture to Hedera’s specific technical properties: high throughput, low and fixed transaction fees, and energy efficiency. For institutional issuers who prefer Hedera’s enterprise-grade technical characteristics over Ethereum’s smart contract platform, the Asset Tokenization Studio provides ERC-3643-compatible issuance without requiring migration to Ethereum.
ERC-7518: Multi-Jurisdictional Compliance
ERC-7518 is an emerging extension standard specifically designed to handle multi-jurisdictional compliance rules within a single tokenized instrument. Where the base ERC-3643 standard implements a single compliance module, ERC-7518 enables the specification of different eligibility rules for different investor jurisdictions within the same token contract — allowing a global tokenized bond to enforce EU MiCA requirements for European investors and SEC Rule 144A requirements for US accredited investors from the same contract, without requiring separate token deployments per jurisdiction. For multi-jurisdiction platforms like Blockmaze, ERC-7518’s multi-compliance module architecture is directly relevant to the challenge of distributing a single tokenized instrument compliantly across eight different regulatory jurisdictions simultaneously.
Layer 2 Deployment for Cost Efficiency
Deploying ERC-3643 tokens on Ethereum’s mainnet involves gas costs that scale with transaction volume. For institutional issuances with large investor bases and frequent secondary market activity, mainnet deployment costs can be material. Layer 2 networks (Polygon, Arbitrum, Optimism) and their EVM-compatible smart contract environments support ERC-3643 deployment with gas costs 10-100x lower than Ethereum mainnet, while inheriting Ethereum’s security guarantees. DTCC’s Collateral AppChain (using Chainlink on an Avalanche subnet), Polygon CDK’s enterprise chains, and other institutional Layer 2 initiatives are all designed to support ERC-3643-compatible compliance architecture at institutional transaction volumes.
ONCHAINID: The Identity Layer Evolution
The most consequential evolution in the ERC-3643 ecosystem is happening at the identity layer rather than the token standard itself. ONCHAINID is the on-chain identity protocol that ERC-3643 compliance modules use to verify investor eligibility. In the current model, each platform deploying ERC-3643 tokens maintains its own identity registry — meaning an investor who is KYB/KYC verified on one platform must reverify on every other platform to access different tokenized instruments.
The ONCHAINID ecosystem is moving toward a shared identity model where a single ONCHAINID identity, issued by a trusted identity issuer, is recognised by multiple tokenized securities platforms without requiring separate reverification. This would make the investor’s KYB/KYC credential portable — verified once, recognised everywhere that accepts the identity issuer’s attestation. The vision is close to what the EU’s EIDAS 2.0 digital identity framework is pursuing at the government level: a single digital identity that works across all regulated services.
The Decision Tree for Institutional Issuers in 2026
| Use Case | Recommended Standard | Reason |
|---|---|---|
| Regulated securities with KYB/KYC and transfer restrictions | ERC-3643 (T-REX) | Institutional default; SEC endorsed; DTCC and MAS Project Guardian built on it; broadest ecosystem support |
| Multi-jurisdiction regulated securities | ERC-3643 + ERC-7518 extension | Multi-compliance module enables jurisdiction-specific rules in single contract |
| Hedera-native institutional deployment | Hedera Asset Tokenization Studio (ERC-3643 wrapper) | ERC-3643 compliance architecture on Hedera’s enterprise technical properties |
| Permissionless tokens without compliance requirements | ERC-20 | Universal standard; broadest DeFi composability; no compliance overhead needed |
| Multi-asset fractional ownership (multiple asset types, single contract) | ERC-1155 | Efficient for portfolios of assets where single contract manages multiple token types |
| Enterprise/private blockchain deployment | Canton Network (Daml) or Hyperledger Fabric | Private blockchain environments where Ethereum-native standards don’t apply |
Disclaimer: This article is for informational purposes only and does not constitute financial or legal advice. Readers should conduct their own research and consult with qualified professionals before making any investment or business decisions.
Frequently Asked Questions
1. What is ERC-3643?
An Ethereum token standard developed by Tokeny that extends ERC-20 with a mandatory compliance layer: every transfer is checked against an identity registry before execution, enforcing KYB/KYC requirements and transfer restrictions at the smart contract level. The T-REX protocol is the open-source reference implementation.
2. Why did the SEC Chairman cite ERC-3643 in a July 2025 speech?
ERC-3643’s adoption as the institutional tokenized securities standard had reached the level where the SEC’s leadership engaged with it as a specific, named technical standard rather than a generic blockchain concept. With DTCC ComposerX and the broader Project Guardian built on it, and $32B+ tokenized across 180 jurisdictions, ERC-3643 is operating at regulatory-attention scale.
3. What is ERC-7518?
An emerging extension to ERC-3643 that enables multi-jurisdictional compliance rules within a single token contract — allowing different eligibility rules for investors in different jurisdictions from the same token deployment, rather than requiring separate contracts per jurisdiction.
4. How does Hedera’s Asset Tokenization Studio relate to ERC-3643?
Hedera integrated ERC-3643 into its Asset Tokenization Studio in December 2025, allowing institutional issuers to deploy ERC-3643-compliant tokenized bonds and equities on Hedera’s enterprise blockchain with its high throughput and fixed transaction fees.
5. What is ONCHAINID and why is its evolution significant?
ONCHAINID is the on-chain identity protocol that ERC-3643 compliance modules use to verify investor eligibility. Its evolution toward a shared, portable identity model — where a single ONCHAINID is recognised across multiple platforms without separate reverification — would make institutional investor identity credentials portable, reducing the redundant KYB/KYC overhead of the current per-platform model.