Interchain Communication
Identification related ERCs
| ERC | Title | Description |
|---|---|---|
| EIP-3220 | Crosschain Identifier Specification | A self-verifying unique blockchain identifier that deals with forks. |
| EIP-2228 | Canonicalize the name of network ID 1 and chain ID 1 | The Ethereum network with network ID 1 and chain ID 1 is named Ethereum Mainnet. |
| ERC-2193 | dType Alias Extension - Decentralized Type System | We are proposing Alias - a semantic standard for identifying on-chain resources by human-readable qualifiers, supporting any type of data. |
| ERC-7930 | Interoperable Addresses | An extensible binary format to refer to an address specific to one chain. |
Invocations related ERCs
| ERC | Title | Description |
|---|---|---|
| ERC-6944 | ERC-5219 Resolve Mode | Adds an ERC-4804 resolveMode to support ERC-5219 requests |
| EIP-2696 | JavaScript `request` method RPC transport | A standard for remote procedure calls between an Ethereum Provider and an Ethereum Client when both are able to interface with each other via a shared JavaScript object. |
| EIP-2700 | JavaScript Provider Event Emitter | A standard mechanism for JavaScript Ethereum Providers to notify clients about chain state changes when both are able to interface with each other via a shared JavaScript object. |
Routing related ERCs
| ERC | Title | Description |
|---|---|---|
| ERC-7888 | Crosschain Broadcaster | Trustless storage-based message broadcasting for rollups. |
| ERC-7884 | Operation Router | A protocol that enables smart contracts to redirect write operations to external systems. |
| ERC-7746 | Composable Security Middleware Hooks | An interface for composable, runtime security checks in smart contracts. |
| ERC-7700 | Cross-chain Storage Router Protocol | Provides a mechanism to replace L1 storage with L2 and databases through cross-chain routers |
| ERC-6120 | Universal Token Router | A singleton router contract allows tokens to be spent in the transfer-and-call pattern instead of approve-then-call. |
| ERC-2746 | Rules Engine Standard | An interface for using a smart contract as a rules engine. A single deployed contract can register a data domain, create sets of rules that perform actions on that domain, and then invoke a set as an atomic transaction. |
| ERC-7615 | Atomic Push-based Data Feed Among Contracts | An Atomic Mechanism to Allow Publisher Contract Push Data to Subcriber Contracts |
| ERC-5219 | Contract Resource Requests | Allows the requesting of resources from contracts |
Verification related ERCs
| ERC | Title | Description |
|---|---|---|
| ERC-1271 | Standard Signature Validation Method for Contracts | Standard way to verify a signature when the account is a smart contract |
| EIP-6051 | Private Key Encapsulation | defines a specification for encapsulating private keys. |
| ERC-5719 | Signature replacement interface | Non-interactive replacing of smart contract wallet signatures that became stale due to configuration changes. |
| ERC-5437 | Security Contact Interface | An interface for security notice using asymmetric encryption |
| ERC-7965 | Proof-based Broadcast in ERC-7786 Gateways | Cross-chain messaging using cryptographic proofs to verify messages between blockchains. |
Messaging related ERCs
| ERC | Title | Description |
|---|---|---|
| ERC-7786 | Cross-Chain Messaging Gateway | An interface for contracts to send and receive cross-chain messages containing arbitrary data. |
| ERC-7627 | Secure Messaging Protocol | End-to-end encryption for sending messages between users. |
| ERC-6170 | Cross-Chain Messaging Interface | A common smart contract interface for interacting with messaging protocols. |
Execution related ERCs
| ERC | Title | Description |
|---|---|---|
| ERC-5164 | Cross-Chain Execution | Defines an interface that supports execution across EVM networks. |