A bridge is the most attacked component in the industry and the one most often announced before it exists. EmpoorioChain's is in a clear state: evaluated, designed, not built. This post is the evaluation and the status.
What the chain has
- BEEFY and MMR in the runtime — compact finality commitments a light client on another chain can verify.
pallet-dracma-bridge,pallet-dracma-sync,pallet-dracma-ics20(runtime indexes 19, 33, 35) — accounting for locked and minted representations, and an IBC-style transfer flow.- An XCM suite (
pallet-xcm,pallet-xcmp) for Substrate-to-Substrate messaging. - A relayer codebase with Substrate and REST clients in the Dracma repository, and a
/bridge/fee_quoteendpoint.
What was compared
| Snowbridge | Hyperbridge | LayerZero | |
|---|---|---|---|
| Trust model | Trustless: BEEFY light client on Ethereum + beacon light client on Substrate | Cryptoeconomic, ISMP | Configurable verifier network |
| Fit with EmpoorioChain | High — BEEFY already in runtime | Medium | Medium; external operators |
| Integration effort | High — beacon light client + gateway contracts | Medium | Low |
| Latency | ~15 min (Ethereum beacon finality) | Minutes | Minutes |
| Censorship resistance | High — no external operators | Medium | Depends on verifier set |
| Testnet available | Yes | Yes | Yes |
Decision: Snowbridge as the primary design, with native XCM for Substrate chains. The reasoning: it is the only option whose security reduces to the two chains' own consensus, and EmpoorioChain already produces the BEEFY commitments it needs.
What is missing
From the evaluation's own list: a functional Ethereum testnet bridge with replay protection; a bridge threat model; bridge UX in Eoonia; indexing of bridge messages in EmpooScan. The mainnet gate lists testnet bridge — deposit, withdraw, timeout, end to end as blocking and unchecked.
The wrapped token that exists
On Sepolia there is a wDMS ERC-20 (215 M supply) from an earlier bridge design, with an escrow of zero — it represents no DMS and cannot be redeemed. The ecosystem corrected 25 documents that implied otherwise. Its owner-side disposition is an open decision. It is evidence that the earlier approach was abandoned, not that a bridge exists.
The two "bridges" that do work
Within EmpoorioChain, moving DMS between the native and EVM sides needs no bridge — it is one ledger. And Eoonia holds DMS and ETH on their respective chains as first-class assets without moving either across. Both are sometimes described as bridging; neither is.
Why not ship something faster
Because a bridge with a compromised verifier set is how chains lose everything at once, and the ecosystem's own threat model lists bridge replay and escrow mismatch among its top runtime threats. A slow, trustless design that does not exist yet is preferable to a fast one that does. This page will change when there is a deposit, a withdrawal and a timeout to point at on EmpooScan.
Based on BRIDGE_EVALUATION.md (2026-05-29, corrected 2026-09-05), CONTRATOS_EVM.json, THREAT_MODEL.md and MAINNET_GATE.md Gate 2.