ERC-3475 primary sources — 2026-05-12

What I reviewed

Key takeaways from primary sources

  • ERC-3475 models obligations through a classId / nonceId grid, where each class can contain many issuance or redemption states.
  • The standard is batch-native: transfer, issue, redeem, burn, and approve all work over Transaction[] bundles rather than forcing one-instrument-at-a-time flows.
  • It keeps multiple supply states explicit (total, active, redeemed, burned) instead of flattening the lifecycle into one balance number.
  • It standardizes class-level and nonce-level metadata/value access, which makes obligation terms, descriptions, and redemption conditions a visible interface layer.
  • The spec explicitly centers issuer/controller power via the Bank role, which issues, redeems, or burns once conditions are satisfied.
  • Debond’s README frames the intended use case clearly: richer LP-token / obligation structures where one ERC-20 balance cannot express multiple redemption dates, conditions, and secondary-market divisions.

Specific source signals worth retaining

  • EIP abstract and motivation: strongest sources for why the authors thought existing ERC-20 / ERC-721 / ERC-1155 patterns were insufficient for obligation-heavy instruments.
  • EIP function set: best source for the lifecycle split among issue, redeem, burn, batched transfer, progress tracking, and metadata/value access.
  • EIP rationale language around metadata and batching: useful for understanding this as an onchain obligation-state standard, not merely as a bond label.
  • Debond README: useful narrative source for the product intuition that class/nonce structure is meant to support multiple callable bonds and more expressive redemption logic than ordinary LP tokens.

Why this entry belongs in the corpus

  • It gives the tokenization cluster a clean lower-layer comparison point for issuer-controlled obligation state, maturity logic, and metadata-rich redemption conditions.
  • It helps separate bond-style lifecycle control from later compliance, identity, and transfer-restriction systems.
  • The durable insight is that many tokenized assets are really families of obligations with differentiated issuance and redemption states, and ERC-3475 makes that structure legible at the interface level.