Cowrie Research

erc-7726

3 min read

ERC-7726

  • Name: ERC-7726 (Common Quote Oracle)
  • URL: https://eips.ethereum.org/EIPS/eip-7726
  • Category: oracle quote-interface standard / oracle-consumption middleware / amount-based valuation primitive
  • Summary: ERC-7726 is a quote interface, not an oracle network. It standardizes getQuote(baseAmount, base, quote) so integrators stop hand-rolling decimal normalization around provider-specific price feeds. Useful because it makes the adapter layer explicit; the hard part still sits in freshness, validity, and routing policy, which the standard pointedly does not solve.
  • What it does:
    • Standardizes a minimal onchain interface for asking how much of quote is equivalent to a given baseAmount of base
    • Forces consumers to request concrete asset amounts rather than raw decimal price factors
    • Pushes decimal conversion and pair-specific normalization into oracle implementations and adapters rather than every integrating protocol
    • Defines canonical placeholder addresses for assets without contract addresses such as ETH and BTC, and a convention for ISO-4217-coded fiat assets
    • Keeps the interface narrow enough that many existing oracle systems can be wrapped behind it without changing their underlying trust model
  • Key claims:
    • The EIP motivation is explicit that oracle integration is fragmented across many APIs and that protocols repeatedly build custom adapter layers. ERC-7726 exists to compress that duplicated integration work into one shared interface.
    • The most important mechanism insight is the move from price to quote. Consumers ask for the value of a concrete asset amount, which means adapter contracts can handle decimals internally and consumers can stay agnostic to provider-specific fixed-point conventions.
    • The spec intentionally omits a getPrice function. Its rationale says decimal prices are awkward onchain and that a whole-unit price is just a special case of getQuote, which makes quote semantics the true primitive.
    • The standard also intentionally omits validity or freshness metadata. Its security section says implementations, not the standard, must publish the conditions under which their data should be trusted. That means interface standardization does not remove oracle-selection risk; it relocates it into adapter and provider policy.
    • Special-address handling is analytically useful because it extends the interface beyond ERC-20 pairs. ETH, BTC, and even ISO-4217-coded fiat units can be represented in the same quoting API, which helps explain why the standard is a valuation interface rather than a token-only price-feed wrapper.
    • Euler Price Oracles provide the clearest reference implementation context. Their repo and whitepaper explicitly frame IPriceOracle as a quote-based interface compatible with ERC-7726, show how adapters normalize heterogeneous providers behind that API, and extend the idea with getQuotes bid/ask support above the narrower standard.
    • ERC-7726 belongs in the active corpus because it gives the oracle cluster a lower-layer consumption standard that makes adapter responsibility, decimal normalization, and validity-policy omission visible instead of burying them inside one provider brand.
  • Whitepaper: No standalone ERC-7726 whitepaper surfaced in this pass. The strongest primary materials were the canonical EIP text and Euler’s official IPriceOracle materials collected in ../../whitepapers/erc-7726-primary-sources-2026-05-12.md.
  • Sources:

Internal linkages

Graph View

Backlinks