ERC-7802

  • Name: ERC-7802 (Token With Mint/Burn Access Across Chains)
  • URL: https://eips.ethereum.org/EIPS/eip-7802
  • Category: crosschain token interface standard / bridge-facing mint-burn token surface / thin interoperability layer
  • Summary: ERC-7802 is best understood as a minimal token-side interface for crosschain mint/burn flows, not as a full bridge framework or sovereign-token governance system. Its core move is to standardize crosschainMint and crosschainBurn as dedicated bridge entry points, plus explicit CrosschainMint / CrosschainBurn events and ERC-165 interface detection, so burn/mint bridges can target one common token surface instead of each inventing a bespoke extension. The reusable mechanism insight is that ERC-7802 standardizes the token hook layer while deliberately leaving bridge admission, quotas, fees, and broader multichain governance outside the base spec.
  • What it does:
    • Defines a minimal IERC7802 interface with crosschainMint(address,uint256) and crosschainBurn(address,uint256) for authorized bridge contracts
    • Adds dedicated crosschain events so indexers and auditors can distinguish bridge mint/burn activity from ordinary local token issuance and destruction
    • Uses ERC-165 introspection so integrators can verify that a token exposes both crosschain entry points
    • Preserves backwards compatibility with ERC-20 while allowing extra controls like rate limits or fee logic to be layered on top
    • Lets issuers keep bridge-specific access control outside the interface instead of hard-coding one canonical bridge design into the token standard
    • Supports migration paths for legacy ERC-20s through lockbox-style wrappers rather than requiring every existing token to be natively mintable
  • Key claims:
    • The EIP abstract explicitly frames ERC-7802 as a minimal and extensible interface for standardized crosschain communication, which is the clearest reason to catalog it as a thin interoperability primitive rather than a full bridge product
    • The motivation says interface fragmentation among canonical and third-party bridges is the main problem being solved, which makes ERC-7802 analytically useful as a common-denominator token hook layer beneath many bridge systems
    • The rationale emphasizes bridge agnosticism and says tokens should stay simple while bridges contain crosschain logic, showing that the standard is intentionally trying to keep governance and routing decisions out of the base token contract
    • The spec separates local mint/burn from crosschain mint/burn, which matters because it isolates bridge-authorized supply relocation from ordinary issuance policy instead of flattening both into one generic admin mint surface
    • ERC-165 support is important because it gives local integrators a clean way to verify the interface shape, while the EIP also explicitly notes that remote-chain consistency is still the bridge’s responsibility
    • The backwards-compatibility section points to lockbox-style migration for non-upgradable tokens, which makes ERC-7802 a useful comparison point against xERC20 / ERC-7281 rather than a replacement for issuer-controlled quota systems
    • Optimism’s SuperchainERC20 starter materials are a strong implementation signal: they treat ERC-7802 as the standardized mint/burn rail beneath Superchain-native fungibility, while still keeping bridge permissioning and same-address deployment policy outside the bare interface
    • The wrapped-native-token caveat is analytically important because it shows the standard does not itself guarantee collateral safety; the bridge topology and underlying asset control still determine whether minting is actually safe
  • Whitepaper: No standalone ERC-7802 whitepaper surfaced in this pass. The strongest primary materials were the draft ERC text and Optimism’s SuperchainERC20 implementation materials collected in ../../whitepapers/erc-7802-primary-sources-2026-05-14.md.
  • Sources:

Internal linkages

  • Closest richer sibling: erc-7281.

  • Stronger transfer stacks that add the governance or routing layers this interface omits: cctp and chainlink-ccip.

  • Reusable question: who controls verifier choice, bridge admission, and collateral discipline once the token exposes the hook?

  • Last reviewed: 2026-06-03 UTC