Category: named-parameter bond token standard / ERC-20-like fixed-income primitive / cross-chain bond interface
Summary: ERC-7092 is worth cataloging not as just another bond token EIP, but as a deliberate attempt to make onchain bonds look more like familiar fixed-income instruments and less like abstract multi-dimensional token grids. Its core move is to keep transfer and allowance behavior close to ERC-20-style expectations while naming the financial fields directly: ISIN, currency, denomination, issue volume, coupon rate, issue date, maturity date, and per-account principal. Around that baseline it adds optional interfaces for coupon metadata and cross-chain operations. That makes ERC-7092 analytically useful because it exposes a different answer to tokenized-debt design than ERC-3475 or ERC-3525: instead of modeling obligations through class/nonce matrices or semi-fungible slots, it standardizes a flatter bond-shaped interface whose main value is operational legibility for issuers, wallets, and secondary-market tooling.
What it does:
Defines a core bond-token interface with named getters for isin, currency, denomination, issueVolume, couponRate, issueDate, maturityDate, and principalOf
Keeps holder movement and delegation close to ERC-20-like patterns through approve, decreaseAllowance, transfer, and transferFrom, while allowing a bytes payload on transfers
Adds optional batch approval and batch transfer functions for portfolio-style bond operations
Adds an optional IERC7092ESG interface for decimals, coupon currency, coupon type, coupon frequency, and day-count basis
Adds an optional IERC7092CrossChain interface for approvals, transfers, and redemptions targeting a named destination chain and destination bond contract
Explicitly contemplates extension into callable, puttable, and convertible bond variants through inheritance from the reference implementation described by the EIP
Key claims:
The motivation section is unusually revealing: ERC-7092 is pitched against ERC-3475 specifically because the authors see class/nonce abstractions and metadata-index indirection as too unfamiliar and too gas-heavy for straightforward bond issuance.
The important reusable insight is therefore not just bonds onchain, but a choice about representation. ERC-7092 makes bond semantics first-class named fields instead of asking developers to reconstruct them from generic metadata grids.
This means ERC-7092 is best understood as the named-parameter bond baseline. Relative to ERC-3475, it sacrifices some generality in favor of direct financial readability. Relative to ERC-3525, it is less about semi-fungible balance topology and more about plain fixed-income lifecycle fields.
The optional ESG interface matters analytically because it separates the minimal debt token from richer coupon and accounting conventions. Coupon currency, coupon type, coupon frequency, and day-count basis become explicit extension surfaces rather than assumptions hidden in offchain documents.
The optional cross-chain interface is also notable. ERC-7092 assumes bond management may span multiple chains and turns destination-chain targeting into part of the standard rather than leaving it entirely to bridge wrappers.
The durable reason to keep ERC-7092 in the corpus is that it makes a distinct lower-middle design choice visible: a bond standard can flatten debt instruments into an ERC-20-like interface with named fixed-income fields rather than adopting a more abstract obligation framework.
Whitepaper: No standalone ERC-7092 whitepaper surfaced in this pass. The strongest reviewed primary materials were the canonical EIP text and linked discussion page collected in ../../whitepapers/erc-7092-primary-sources-2026-05-13.md.