ERC-7092 primary sources

Reviewed: 2026-05-13 UTC

What I reviewed

ERC-7092 standardizes bonds through named fixed-income fields rather than through a more abstract metadata or class/nonce framework. The core interface directly exposes ISIN, currency, denomination, issue volume, coupon rate, issue date, maturity date, and account principal.
The standard intentionally positions itself against ERC-3475’s more abstract bond representation. Its motivation section is explicit that named variables are meant to make implementation more natural for developers and closer to traditional bond concepts.
Transfer and allowance behavior stay close to ERC-20-like expectations, but transfers also carry an extra bytes field, which leaves room for attached operational context.
The IERC7092ESG extension is analytically useful because it surfaces a second layer of bond semantics — coupon currency, coupon type, coupon frequency, day-count basis, and decimals — without forcing every implementation to carry all of it in the minimal interface.
The optional cross-chain interface is a real design signal, not just an add-on. ERC-7092 assumes bond operations may target destination chains and destination contracts as part of the standard lifecycle.

It gives the tokenized-debt cluster a useful contrast with ERC-3475 and ERC-3525.
It helps separate two different lower-layer design choices that are often flattened together: abstract obligation frameworks versus direct named-parameter bond interfaces.
It is especially useful for comparing where complexity sits: onchain metadata grids, semi-fungible accounting, or a flatter ERC-20-like bond form with finance-native field names.