Cowrie Research

erc-7683

4 min read

ERC-7683

  • Name: ERC-7683 (Cross Chain Intents)
  • URL: https://eips.ethereum.org/EIPS/eip-7683
  • Category: cross-chain intent standard / filler-network interoperability rail / order-and-settlement interface
  • Summary: ERC-7683 is best understood as a shared order-expression and settlement-interface standard for cross-chain intent systems rather than as a bridge, wallet, or standalone protocol. Its core move is to standardize the envelope that users sign, the way orders are resolved into filler-readable requirements, and the minimum origin/destination settler interfaces, while leaving pricing, verification, and settlement details implementation-specific. The reusable mechanism is that ERC-7683 tries to commoditize the outer order format so filler networks, routing layers, and settlement systems can interoperate instead of remaining locked inside one bridge or solver stack.
  • What it does:
    • Defines standardized GaslessCrossChainOrder and OnchainCrossChainOrder structs for cross-chain intents
    • Requires implementations to resolve opaque orderData into a generic ResolvedCrossChainOrder that fillers can price and execute
    • Standardizes the Open event plus origin- and destination-side settler interfaces so different intent systems can expose a common integration surface
    • Supports both offchain-signed, filler-opened orders and user-opened onchain orders
    • Lets implementations keep their own pricing logic, fulfillment constraints, verification systems, and settlement procedures inside opaque sub-types and settlement layers
    • Explicitly supports multi-leg fills and arbitrary destination-chain actions through extensible order sub-types rather than limiting the standard to plain token bridging
  • Key claims:
    • The draft ERC says the goal is to let cross-chain value-transfer systems share infrastructure such as order dissemination services and filler networks, which is the clearest reason to catalog it as interoperability rail infrastructure rather than a single app feature
    • The specification’s main architectural move is to separate a standard outer order shell from implementation-specific orderData, which lets very different intent systems interoperate without forcing one pricing or proof model
    • The ResolvedCrossChainOrder abstraction matters because it converts arbitrary order payloads into a common filler-facing description of max liabilities, minimum receipts, and per-leg fill instructions
    • The FillInstruction design keeps originData opaque, meaning the standard deliberately preserves freedom for custom settlement logic while still giving fillers a predictable execution interface
    • The rationale explicitly says pricing can use origin- or destination-side dutch auctions, oracle-based pricing, custom settlement procedures, and different ordering between open and fill, so ERC-7683 is a coordination layer above many different market designs rather than one unified protocol
    • The spec uses bytes32 for foreign addresses to preserve compatibility with non-EVM sibling standards, which shows the authors want the standard to sit at a wider interop boundary than just EVM-to-EVM bridging
    • The spec’s Permit2 discussion is analytically important because it couples token approval and order authorization into one witness flow, making token pull rights and intent consent part of the same user-signing surface
    • The ERC-7683 site and FAQ frame the standard as a way for relayers/fillers to support many protocols from day one, which suggests practical power may still concentrate in shared filler networks, settler implementations, subtype conventions, and dominant order-distribution channels even if the outer format is standardized
    • Across’s launch post says the proposal was introduced jointly by Across and Uniswap Labs so systems like Across and UniswapX can share a universal filler network, which is useful evidence that the standard emerged from converging solver-market architectures rather than abstract standards work alone
  • Whitepaper: No standalone whitepaper or formal research paper surfaced in this pass. The clearest primary sources were the draft ERC, the ERC-7683 documentation site, and the original Across announcement; see ../../whitepapers/erc-7683-primary-sources-2026-05-09.md.
  • Sources:

Internal linkages

  • Production routing anchor that helped push the shared filler-network framing into the open: across

  • Full-stack implementation and middleware layer that turns the standard into concrete settler and solver workflows: open-intents-framework

  • Lower-level settlement sibling that standardizes fulfiller proof and destination-call execution more directly than intent expression: rip-7755

  • Last reviewed: 2026-05-09 UTC

Graph View

Backlinks