erc-6123-primary-sources-2026-05-13

ERC-6123 primary sources

Reviewed: 2026-05-13 UTC

What I reviewed

• Canonical specification:
  • https://eips.ethereum.org/EIPS/eip-6123
  • https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-6123.md
• Reference implementation asset:
  • https://eips.ethereum.org/assets/eip-6123/contracts/SDCSingleTrade.sol
• Official discussion link:
  • https://ethereum-magicians.org/t/eip-6123-smart-derivative-contract-frictionless-processing-of-financial-derivatives/12134

Key takeaways from primary sources

• ERC-6123 is a lifecycle protocol for bilateral financial contracts, not merely a token standard. Its main surfaces are trade inception, trade confirmation, mutual termination, settlement initiation, valuation callback, transfer callback, and failure handling.
• The central architectural move is deterministic process specification. The EIP frames Smart Derivative Contracts as finite-state machines whose trade and post-trade logic are known in advance over the whole contract life cycle.
• Practical authority in this design sits partly in the valuation layer: settlement amounts may come from an external oracle or valuation service that feeds performSettlement, which means model governance and oracle trust are first-class control surfaces.
• The reference SDCSingleTrade.sol makes the state-machine character concrete. It uses explicit states like Inactive, Incepted, Confirmed, Valuation, InTransfer, Settled, InTermination, and Terminated, with modifiers acting as process guards.
• The async settlement callback pattern is a major reusable insight. ERC-6123 is designed for environments where actual payment transfer may complete later and signal success or failure back into the contract through afterTransfer.
• The EIP explicitly says the same lifecycle catalogue can support settle-to-market OTC derivatives, collateralized derivatives, defaultable derivatives, and smart bond contracts, which makes it a useful comparison point across more than one asset class.

Why this entry belongs in the corpus

• It gives the corpus a lower-layer comparison point beneath tokenized bonds and regulated-asset wrappers: the contract-processing protocol itself.
• It helps separate instrument representation from lifecycle orchestration. Many tokenization systems discuss tokens, coupons, or transfers without making trade confirmation, valuation, settlement, and termination equally explicit.
• It is especially useful when comparing ERC-6123 against ERC-7092, ERC-3475, ERC-3525, OTC-derivative digitization efforts, and oracle-governed settlement systems.