ERC-3643 vs ERC-1400: Which Security Token Standard Should You Use in 2026?

Two standards dominate regulated security token development in 2026 — ERC-3643 and ERC-1400. Both enforce transfer restrictions on-chain. Both support KYC/AML compliance. But they take fundamentally different approaches to identity, compliance architecture, and transfer control. Choosing the wrong standard for your RWA tokenization project means rebuilding your compliance layer later — an expensive mistake when you have institutional investors and regulatory requirements on the line. Use the free Blockhertz AI Smart Contract Auditor to check your security token contracts before deployment regardless of which standard you choose.

---

Quick Answer: ERC-3643 vs ERC-1400

---

What is ERC-3643?

ERC-3643, also known as the T-REX standard (Token for Regulated EXchanges), is an Ethereum token standard developed by Tokeny Solutions and formalized as an EIP in 2023. It enforces transfer restrictions through an on-chain identity registry — every transfer is checked against a KYC-verified whitelist before it executes. The compliance layer is modular and separate from the token contract, allowing compliance rules to be updated without touching the token itself.

ERC-3643 is the most widely deployed security token standard in Europe and the Middle East. BlackRock's BUIDL fund, multiple real estate tokenization platforms, and sovereign wealth fund RWA programs use ERC-3643 as their token architecture. Our complete ERC-3643 guide covers the full T-REX architecture in detail.

What is ERC-1400?

ERC-1400, also known as the ST-20 standard, is a security token standard developed by Polymath and proposed as an EIP in 2018. It introduces the concept of token partitions — different tranches of the same token with different transfer rules. A single ERC-1400 token can have a Reg D partition for accredited US investors, a Reg S partition for non-US investors, and a general partition for different jurisdictions, each with its own transfer restrictions. ERC-1400 also natively supports document attachment — compliance documents, offering memoranda and investor agreements can be referenced directly on the token contract.

---

ERC-3643 vs ERC-1400 — Complete Comparison

Feature	ERC-3643 (T-REX)	ERC-1400 (ST-20)
Compliance approach	Identity registry + modular compliance module	Partition-based transfer restrictions
KYC/AML enforcement	On-chain identity registry (ONCHAINID)	Transfer controller (off-chain or on-chain)
Transfer restriction	canTransfer() checks identity + compliance	canTransferByPartition() checks partition rules
Investor categorization	Claims on identity (KYC, country, accreditation)	Token partitions (Reg D, Reg S, etc.)
Document management	Not native (handled externally)	Native document attachment on token
Modularity	Very high (separate compliance module)	Moderate (partition controllers)
Upgradeability	Compliance module upgradeable independently	Transfer controller upgradeable
Institutional adoption	High (Europe, Middle East, Asia)	Moderate (North America focus)
Open source reference	Tokeny T-REX (github.com/TokenySolutions)	Polymath ST-20 (github.com/polymath-network)
EIP status	ERC-3643 (2023)	ERC-1400 (proposed, not finalized)
DeFi compatibility	Limited (permissioned transfers)	Limited (permissioned transfers)
Gas efficiency	Higher gas (external identity calls)	Moderate gas (partition logic)

---

Architecture Comparison

ERC-3643 Architecture

ERC-3643 separates identity from compliance. The token contract knows nothing about KYC rules — it simply checks the identity registry and compliance module before every transfer. This creates a clean separation of concerns: the token handles balances and transfers, the identity registry handles investor verification, and the compliance module handles business rules.

ERC-3643 Architecture:

Token Contract
    ↓ checks before transfer
Identity Registry ← ONCHAINID contracts
    ↓ verifies
Compliance Module ← country rules, caps, lockups
    ↓ enforces
Claim Issuers ← KYC providers sign claims

ERC-1400 Architecture

ERC-1400 organizes compliance around partitions. Different investor categories hold tokens in different partitions, and each partition has its own transfer rules enforced by a transfer controller. Document management is built into the token contract itself, allowing offering documents to be referenced on-chain.

ERC-1400 Architecture:

Token Contract
    ↓ partitions
Partition A (Reg D) ← US accredited investors
Partition B (Reg S) ← Non-US investors
Partition C (General) ← Other jurisdictions
    ↓ each partition has
Transfer Controller ← enforces partition rules
Document Registry ← attached compliance docs

---

When to Choose ERC-3643

ERC-3643 is the better choice when:

• Your investors are globally distributed and need individual-level KYC verification enforced on-chain
• You are building in Europe, the Middle East, or Asia where T-REX has the strongest institutional adoption
• Your compliance rules are complex and likely to change — the modular compliance module can be updated without touching the token
• You need strong investor privacy — ONCHAINID separates identity from token holdings
• You are building a real estate, bond, or RWA platform where individual investor eligibility matters more than investor categorization
• You want to use Tokeny's infrastructure and KYC provider ecosystem

When to Choose ERC-1400

ERC-1400 is the better choice when:

• You are offering securities under US regulations (Reg D, Reg S, Reg A) and need clear partition-based investor categorization
• Your offering requires multiple tranches with different rights and transfer rules
• You need native document management — offering memoranda, subscription agreements and compliance documents attached directly to the token
• You are using Polymath's infrastructure or North American security token platforms
• Your investor categorization is more important than individual investor identity verification

---

Security Vulnerabilities — ERC-3643 vs ERC-1400

Both standards introduce attack surfaces beyond standard ERC-20. The key vulnerabilities differ by architecture.

Vulnerability	ERC-3643	ERC-1400
Access control failure	AGENT_ROLE on identity registry ← most common	Transfer controller admin ← most common
Compliance bypass	Direct compliance module manipulation	Partition controller replacement
Identity spoofing	Trusted claim issuer compromise	Transfer controller whitelist manipulation
Transfer restriction bypass	canTransfer() return value ignored	canTransferByPartition() not enforced
Forced transfer abuse	AGENT_ROLE can move any tokens	Controller can force transfer any partition

Run the free Blockhertz AI Smart Contract Auditor on your ERC-3643 or ERC-1400 contracts — it checks for access control failures, compliance bypass, and reentrancy in forced transfer functions in under 60 seconds. For Hardhat projects, hardhat-blockhertz audits your security token contracts automatically on every commit.

---

ERC-3643 vs ERC-1400 — Which Has More Adoption in 2026?

ERC-3643 has significantly more institutional adoption in 2026, particularly outside North America. The T-REX standard has been deployed by major asset managers, real estate tokenization platforms, and sovereign fund RWA programs across Europe, the UAE, Singapore, and Hong Kong. The ERC-3643 ecosystem includes dedicated KYC providers (Synaps, Sumsub, Shufti Pro), compliance infrastructure, and Tokeny's platform.

ERC-1400 adoption has been stronger in North American security token offerings, particularly Polymath-based platforms and US Reg D/Reg S token offerings. However, the broader institutional RWA market has increasingly standardized on ERC-3643 for new deployments.

Region	Preferred Standard	Reason
Europe	ERC-3643	MiFID II + GDPR-friendly identity model
Middle East (UAE, KSA)	ERC-3643	DIFC/ADGM regulatory alignment
Asia (Singapore, HK)	ERC-3643	MAS/SFC investor eligibility focus
North America	ERC-1400	Reg D/Reg S partition model
Global institutional	ERC-3643	T-REX institutional ecosystem

---

How Blockhertz Builds Security Token Platforms

At Blockhertz we build ERC-3643 security token platforms as our primary standard for RWA tokenization engagements. We have deployed ERC-3643 infrastructure across Ethereum, Polygon, Avalanche, and BNB Chain for real estate, bond, and carbon credit tokenization platforms.

Our open-source ERC-3643 reference implementation is available on GitHub — production-ready contracts for real estate, bonds, and carbon credits, audited by hardhat-blockhertz:

🐙 github.com/Blockhertz/rwa-contracts

We choose ERC-3643 for most client engagements because of its modular compliance architecture, stronger institutional adoption outside North America, and the growing ecosystem of KYC providers and infrastructure built around the T-REX standard. For North American Reg D/Reg S offerings where partition-based compliance is a regulatory requirement, we implement ERC-1400.

Learn more about our RWA tokenization services or book a strategy call to discuss which standard fits your project.

Building a security token platform? Run your contracts through the free Blockhertz AI Smart Contract Auditor — it checks ERC-3643 and ERC-1400 contracts for the most common vulnerabilities in under 60 seconds.

---

Frequently Asked Questions

Is ERC-3643 better than ERC-1400?

ERC-3643 has stronger institutional adoption globally in 2026 and a more modular compliance architecture. ERC-1400 remains the better choice for North American Reg D/Reg S offerings requiring partition-based investor categorization and native document management. The best standard depends on your jurisdiction, regulatory requirements and investor base.

Can I use both ERC-3643 and ERC-1400?

Technically yes — you could build a hybrid architecture — but this adds significant complexity and is rarely justified. Choose one standard based on your primary regulatory jurisdiction and investor base. For most global RWA platforms, ERC-3643 is the correct choice.

Is ERC-1400 an official Ethereum standard?

ERC-1400 was proposed as an EIP but was never finalized as an official Ethereum standard. It remains widely used as an industry convention but lacks the formal EIP finalization that ERC-3643 achieved in 2023. ERC-3643 is a finalized ERC standard.

Which standard does Blockhertz use?

Blockhertz primarily builds on ERC-3643 for RWA tokenization engagements because of its modular compliance architecture, stronger institutional adoption, and the mature T-REX ecosystem. For North American Reg D/Reg S offerings, we implement ERC-1400 where partition-based compliance is a regulatory requirement.

---

Building a security token platform? Talk to the Blockhertz team — we build compliant ERC-3643 and ERC-1400 platforms on Ethereum, Polygon, Avalanche, and BNB Chain.