Erc 1400

What is erc-1400?

ERC-1400 is a family of Ethereum token standards designed for issuing and operating a compliant security token, where transfers can be restricted by rules such as investor eligibility, jurisdiction, lockups, or other compliance requirements. Instead of treating every unit as freely transferable like a typical ERC-20, ERC-1400 introduces patterns for permissioning, auditability, and lifecycle controls that regulated assets often need. It’s commonly discussed in the context of what are security tokens and compliance by code, because it formalises how “who can hold and move this asset” can be enforced at the token-contract level rather than relying only on off-chain processes.

At a high level, ERC-1400 is best understood as a modular framework rather than a single monolithic contract. It groups together multiple Ethereum Improvement Proposals that cover the core needs of regulated tokenisation: validating issuance and redemption, enforcing transfer restrictions with clear failure reasons, supporting “partitions” that separate balances into distinct tranches, attaching legal documents to the token, and enabling special controller actions when required by law or court order. In practice, an ERC-1400 implementation behaves like a permissioned token: wallets, custodians, and exchanges can integrate against predictable interfaces while issuers retain the ability to encode compliance logic (for example, only allow transfers between whitelisted addresses).

Polymath ERC-1400

Polymath is widely associated with ERC-1400 because it helped popularise the idea that security tokens needed a shared, Ethereum-native standard to reduce fragmentation across issuers and platforms. The Polymath approach emphasised interoperability for the security token ecosystem: if multiple issuers follow the same interface expectations for restrictions, document references, and administrative controls, then service providers (like transfer agents, broker-dealers, and compliant exchanges) can support more assets with less custom engineering. This is also why ERC-1400 is often compared with newer compliance-focused standards such as erc 3643, which takes a different design approach to identity and permissioning while pursuing similar goals.

Security token ERC-1400

A security token built with ERC-1400 typically adds three practical capabilities beyond “basic token transfers.” First, it can enforce transfer rules: before a transfer succeeds, the contract can check whether the sender and recipient meet policy requirements (for example, KYC status, accreditation, or jurisdiction constraints) and return a reason code when blocked. Second, it can represent partially fungible holdings using partitions—useful when the same asset needs separate buckets such as locked vs. unlocked shares, different share classes, or tranches with different rights. Third, it can link to off-chain legal materials through on-chain document metadata, helping align the token with offering documents, disclosures, or governing agreements. These features are why ERC-1400 is often described as a permissioned token standard for regulated issuance and secondary transfers.

Why erc-1400 matters

ERC-1400 matters because regulated assets don’t just need “ownership on-chain”—they need enforceable rules around who can hold, transfer, or redeem that ownership. By standardising common compliance and lifecycle patterns, ERC-1400 reduces integration friction for wallets, custodians, and marketplaces that want to support compliant assets at scale. It also creates a shared vocabulary for comparing approaches, which is useful when evaluating erc 3643 vs erc 1400 explained and deciding which model better fits an issuer’s compliance architecture. More broadly, ERC-1400 is a foundational step toward making what are security tokens and compliance by code operational: it turns policy requirements into predictable token behaviours that can be audited and automated across the asset’s lifecycle.