Skip to content

pattern-icma-bdt-data-model.md

Latest commit

 

History

History
53 lines (45 loc) · 2.09 KB

pattern-icma-bdt-data-model.md

File metadata and controls

53 lines (45 loc) · 2.09 KB
title Pattern: ICMA Bond Data Taxonomy (canonical terms/events)
status ready
maturity production
layer offchain
privacy_goal Standardize bond data for clean attestations without exposing raw data
assumptions ICMA BDT schema adoption, schema validator tooling, registrar integration
last_reviewed 2026-01-14
works-best-when
You want machine-readable bond terms/events across tools.
avoid-when
N/A (use as a baseline; extend as needed)
ICMA is not the schema being used for a particular jurisdiction/domain
dependencies
ICMA BDT schema
context i2i
crops_profile
cr os privacy security
none
true
full
high

Intent

Use ICMA Bond Data Taxonomy as the canonical schema for bond terms & lifecycle events to avoid fragmentation and enable clean attestations/proofs.

Ingredients

  • Standards: ICMA BDT
  • Infra: Schema loader/validator; compression (XML→binary)
  • Off-chain: Mapping to registrar records; EAS hash anchoring

Protocol (concise)

  1. Author terms/events in BDT.
  2. Validate; compress; store (on/off-chain hash).
  3. Use same schema in proofs/disclosures.

Guarantees

  • Interop-ready, regulator-friendly data.
  • Easier proofs/attestations.

Trade-offs

  • Up-front mapping effort to existing systems.
  • CROPS context (i2i): CR could reach medium if the BDT schema is published as a permissionless open registry with EAS-anchored contributions and no approval gate. Among institutional counterparties, open schema governance ensures no single issuer or registrar controls the canonical bond data format, enabling competitive issuance platforms to interoperate without gatekeeping.

Example

  • Issuance terms in BDT; hash anchored via EAS; regulator verifies consistency.

See also

  • pattern-crypto-registry-bridge-ewpg-eas.md

See also (external)