ERC-1400 primary sources — 2026-05-12

What I reviewed

• Draft umbrella standard:
  • https://github.com/ethereum/EIPs/issues/1411
• Security Token Standard site:
  • https://thesecuritytokenstandard.org/
• Original umbrella repo / README:
  • https://github.com/SecurityTokenStandard/EIP-Spec
  • https://raw.githubusercontent.com/SecurityTokenStandard/EIP-Spec/master/README.md

Key takeaways from primary sources

• ERC-1400 is not one narrow feature proposal; it is a library-style family that bundles partitioned balances, transfer-validity checks, document management, and controller powers.
• The umbrella design is the main thing worth retaining. The proposal makes early security-token architecture legible as several separate but coordinated interfaces rather than one generic “regulated token” blob.
• The README is especially useful because it frames the whole effort as a foundational block for further standards and admits that offchain compliance processes still remain necessary.
• The requirements list captures the original 2018 security-token design space very clearly: reasoned transfer failure, forced transfer, issuance/redemption, balance-subset metadata, document references, and optional signed offchain approvals.
• The Security Token Standard site preserves older tranche-oriented interface language and ecosystem framing, which helps show how the family was marketed as a reusable substrate for multiple vendors and issuers.

Specific source signals worth retaining

• Draft abstract and motivation: strongest sources for the claim that ERC-1400 is an aggregate of ERC-1410, ERC-1594, ERC-1643, and ERC-1644 rather than a standalone minimal primitive.
• Draft requirements section: best single source for the control surfaces the authors considered essential to onchain securities.
• README objective and introduction: best source for the “foundational block” framing and for the admission that the standard only partially automates compliance.
• Security Token Standard site: useful corroboration that the family was presented as a cross-ecosystem standard rather than a one-company contract flavor.

Why this entry belongs in the corpus

• It gives the tokenization cluster an umbrella comparison point above ERC-1410 / ERC-1594 / ERC-1643 / ERC-1644 instead of forcing each sub-standard to stand alone.
• It helps separate four layers that later products often bundle together: partitioning, transfer permissioning, disclosure, and controller override.
• The durable insight is that many “security token” systems are really policy bundles assembled from multiple narrower control surfaces, and ERC-1400 makes that decomposition explicit.