Interoperability is three different problems wearing one word: messaging between chains, proving one chain's state to another, and storing data that a chain references but should not hold. EmpoorioChain addresses each differently. This post is the map.
Messaging: XCM
EmpoorioChain's runtime includes the XCM suite (pallet-xcm, pallet-xcmp, xcm-runtime-config). XCM is the Polkadot ecosystem's cross-consensus message format; with it, EmpoorioChain can send and receive asset transfers and remote calls with other Substrate chains that speak it. Status: wired in the runtime, no live channel to another chain. Opening one requires a counterparty and a relay or bridge hub, neither of which exists for the testnet today.
Proofs: BEEFY and MMR
pallet-beefy and pallet-mmr (indexes 9 and 8) produce compact commitments to finalized blocks over a Merkle Mountain Range. A light client — in a browser, a wallet, or a contract on another chain — can verify EmpoorioChain finality from a BEEFY signature and an MMR proof without syncing headers. This is what Eoonia's light-client protocol is built on and what the Snowbridge design would use on the Ethereum side. Status: live in the runtime; consumed by Eoonia's protocol design; not yet by any external chain.
Data: the storage market
Some chains solve "data that must outlive the transaction" by pointing at a permanent-storage network. EmpoorioChain has its own: pallet-blob-storage commits, the storage market pays providers by the byte, pallet-storage-oracle verifies availability. A blob commitment costs 0.000095 DMS per MB on the testnet. The provider network is small (the ecosystem's own nodes; Ouranoos is the first consumer), and the design intent for scale — erasure coding with KZG commitments — is a roadmap. But the primitive is native, and referencing an external permanent-storage chain is not required.
EVM: the interoperability everyone already uses
The most exercised interoperability EmpoorioChain has is the boring one: Frontier lets Ethereum tooling talk to it. Since runtime 211 MetaMask and Hardhat transactions are accepted; chain id 2026; one ledger for native and EVM DMS. It is not cross-chain, but it is what most integrations actually need.
What is not here
- A live channel to any other chain.
- A bridge with escrow (see the bridge evaluation post; Snowbridge chosen, not built).
- A partnership or integration with any permanent-storage network.
- A hackathon. The ecosystem's testnet hackathon plan exists — 48 hours, three tracks including infrastructure and tooling — and has not opened, because its faucet and explorer prerequisites are not deployed. The previous version of this page announced an interoperability hackathon with another storage network; nothing of the kind is scheduled.
For a team that wants to build a bridge or a channel
The pieces to start from are BEEFY/MMR (proofs), pallet-dracma-bridge (lock/mint accounting), the XCM configuration, and the relayer skeleton in the Dracma repository. The bridge threat model is the first deliverable the evaluation asks for. When the grants programme opens, infrastructure is one of its five categories.
Based on BRIDGE_EVALUATION.md, PALLET_REFERENCE.md, ARCHITECTURE.md and TESTNET_HACKATHON_PLAN.md.