Moving assets and messages between chains
Stable specification; check network and product support
Final review period before the specification becomes Final
Open for peer review; implementation support varies
Early proposal that may change
ERC-7786 standardizes gateway source/recipient message calls and attributes. Applications can send a message through a compliant gateway, while route discovery, bridge health, status, post-processing, retry, and refunds remain adapter/provider-specific.
Stages: Executing Transactions, Status & Confirmation
ERC-7950 encodes an EIP-155 chain ID and a transaction hash as chainId:txHash:tx. Compatible apps can use that reference for chain-aware lookup and sharing. The reference is not itself an explorer URL or proof of payment, and wallets and explorers choose whether to support it.
Stages: Status & Confirmation
ERC-5164 standardizes message dispatch and destination execution interfaces for cross-chain applications. A bridge adapter can carry a dispatcher message to a destination executor, while bridge selection, timing, security, status, and recovery remain provider-specific.
ERC-7828 defines a human-readable chain-aware name format and ENS chain resolution. Applications can use the resolved chain context to prompt a user to switch networks, while routing and wallet switching remain application behavior with explicit user consent.
Stages: Discovery & Connection, Authentication & Identity +1
ERC-7930 defines a versioned, length-prefixed binary envelope for chain-specific account identifiers. Pair it with a human-readable companion such as ERC-7828 or a CAIP-350 display profile when showing chain context to users; the ERC-7930 wire format is not itself a user-facing prefix string.
Stages: Authentication & Identity, Reading & Understanding +1
ERC-7683 defines a solver-facing resolver interface for opaque cross-chain protocol payloads. Applications can express protocol-specific intents and let resolvers evaluate them, while order shape, settlement, fills, pricing, and recovery remain properties of the selected protocol rather than guarantees of the ERC.
ERC-7811 defines wallet_getAssets for a wallet to report an account's assets, grouped by EIP-155 chain ID with optional filters. An application may build a cross-chain portfolio or net-worth view from those reports, but valuation, aggregation, stale-data policy, and bridged-asset deduplication remain application responsibilities.
Stages: Asset Discovery & Display
