Cross-Chain Governance Snapshot Bridge Tool

WHAT IT DOES

This tool gives governance participants a unified view of cross-chain proposals that originate as off-chain Snapshot votes and are relayed to an on-chain execution bridge on a destination EVM chain. For any proposal ID, it fetches and displays the full Snapshot proposal metadata — title, description, voting options (for/against/abstain), quorum threshold, and current vote tallies per option. It also retrieves the voting power of any specified wallet address on the source chain at the exact block height where the Snapshot snapshot was taken. On the destination side, the tool reads the bridge contract's state to tell you whether the proposal has been relayed, the relay transaction hash, and the current execution status on the destination chain — pending, executed, failed, or challenged. Finally, it reports the source chain's proposal execution status, including timelock schedules and whether the execution call has already been dispatched.

HOW TO USE

Connect your wallet on the destination EVM chain. Enter the Snapshot proposal ID (or the bridge contract's internal proposal ID) and select the source chain (Ethereum mainnet or Gnosis Chain). The tool queries Snapshot's GraphQL API for off-chain vote data and uses archive RPC nodes to check your voting power at the snapshot block. It then reads the destination bridge contract and the executor contract to display relay and execution states. All results appear on a single dashboard — no manual RPC calls, log parsing, or merkle verification steps required from you.

TECHNICAL MECHANISM — CHUNKED LOG SCANNING WITH MERKLE ROOT RELAY

Most cross-chain relay tools fail under public RPC rate limits because they scan source chain event logs in one large range. This bridge tool's backend relayer uses a different approach: it scans source chain logs for finalized proposal roots in 10,000-block chunks. If any chunk times out or returns a rate-limit error, the relayer backs off exponentially and retries only that chunk independently — the rest of the scan continues in parallel. This prevents a single RPC refusal from aborting the entire relay. Once the root is found, the relayer builds a compact merkle tree from all Snapshot votes (including voter address, choice, and voting power) and submits only the root plus the final tally to the destination bridge contract. The bridge verifies the root against a source-chain verifier contract that emits the finalized root after the voting period ends. The tool then reads the bridge's stored merkle root and compares it with the on-chain execution log to determine whether the proposal has been executed.

WHAT IT CANNOT SEE

This tool cannot verify that the source chain's voting process was fully tamper-proof or that off-chain Snapshot signatures are cryptographically valid. It relies entirely on the bridge contract's verification of the relayed merkle root and the source chain's final state as recorded in the verifier contract. It does not validate individual Snapshot signatures, nor does it detect vote-buying, Sybil attacks, or collusion among voters. The bridge's fraud-proof mechanism is only as secure as the source chain's finality — deep reorganizations beyond the finality threshold could theoretically invalidate a relayed root. The tool also cannot see proposals that were never relayed or that failed during the relayer's scan due to missing source chain events.

PLEASE NOTE — EVM CHAINS ONLY

This tool supports destination chains that are EVM-compatible — Ethereum, Polygon, Arbitrum, Optimism, Base, and similar networks. Source chains are currently limited to Ethereum mainnet and Gnosis Chain. Non-EVM chains such as Solana, Cosmos, or Sui are not supported. The tool is read-only — it does not submit relay transactions or execute proposals; it only displays state information. Relaying a proposal still requires a separate transaction signed by an authorized relayer or governance executor.