GitHub Repos advanced 3 min read Jun 15, 2026
Public Preview Sign in free for the full digest →

Union Protocol: Zero-Knowledge Blockchain Bridge for Cosmos & Ethereum

“Every major bridge hack since 2022 — Ronin $624M, BNB $568M, Wormhole $326M — came from compromising a trusted committee. Union is the first ZK-only bridge on mainnet that replaces that committee with cryptographic proofs.”

Union Protocol: Zero-Knowledge Blockchain Bridge for Cosmos & Ethereum
1 Views
0 Likes
0 Bookmarks
Source · github.com

“"A Laptop can generate a proof for a 128 validator set within seven seconds using just 5GB of RAM." — Lavender Five (source: https://www.lavenderfive.com/blog/unionbuild-and-zk-ibc)”

You're building a DeFi application that needs to move assets between Ethereum and Cosmos, or between Ethereum and Bitcoin. Every bridge you evaluate — Wormhole, Axelar, LayerZero — relies on a validator set or multisig committee that you have to trust not to be compromised. Wormhole lost $326M in February 2022 when an attacker bypassed that committee's signature verification. You want cross-chain transfers without the counterparty risk, but ZK-based alternatives have historically required expensive proving hardware and taken minutes per proof.

zero-knowledgeblockchaininteroperabilityrustcosmosethereumdefi

Union runs its own Layer 1 blockchain as a routing hub. When you initiate a cross-chain transfer, Union's Galois prover generates a ZK proof that the validators of the source chain signed the transaction's Merkle root — no oracle involved, just cryptographic verification. That proof is submitted on-chain for verification. The key engineering insight: Union replaced Tendermint's Ed25519 signatures with BLS12-377 signatures in its CometBLS consensus engine, enabling BLS aggregation — instead of verifying N individual validator signatures, one aggregated proof covers all of them. This collapsed the ZK circuit from approximately 2 million constraints per validator to a 7-second proof on a laptop with 5 GB RAM. The Voyager relayer handles cross-chain message delivery and compensates provers per packet, making relaying economically sustainable without continuous gas subsidies.

01
No-committee cross-chain verification — ZK proofs replace validator multisigs, so a Wormhole-style $326M exploit requires breaking the underlying cryptographic math, not compromising a 13-of-19 committee
02
Galois ZK prover — generates a 128-validator BFT consensus proof in 7 seconds using 5 GB RAM on consumer hardware, making ZK verification economically feasible for relayers without GPU farms
03
CometBLS consensus engine — BLS12-377 signatures replace Ed25519 in Tendermint, enabling signature aggregation that collapses ZK circuit size and reduces per-block proving costs for the whole network
04
Voyager relayer with per-packet incentives — EPOCH-based validator rotation means light clients do not update every block, so relayers earn fees per packet without absorbing continuous gas costs
05
Multi-VM support — TypeScript SDK, CosmWasm, EVM Solidity, Move, and Cairo let you write bridging logic in your existing stack without rewriting contracts
06
IBC extension to non-Cosmos chains — Ethereum, Sui, BNB Chain, and eventually Solana gain IBC's trust model without running Cosmos infrastructure on their end
Who it’s for

If you're a Rust or Solidity engineer building cross-chain DeFi and have ruled out current bridge options because of their multisig attack surface, Union is worth a close evaluation. Also relevant if you maintain a Cosmos appchain and want to reach EVM ecosystems without operating a centralized bridge. Not suitable yet if you need sub-second cross-chain finality — ZK proof generation adds a minimum 7-second latency floor that rules out real-time arbitrage and gaming state-sync use cases.

Worth exploring

The core ZK architecture is grounded in real cryptography research, and the mainnet has been live since September 2025. The gap between roadmap and current delivery is large — most 2025-2026 roadmap features sit at 0% as of June 2026, and 73,964 GitHub stars with 32 contributors is an unusual ratio. Evaluate for projects where cryptographic trustlessness is a hard requirement and 7+ second latency per bridge call is acceptable.

Developer playbook
Tech stack, code snippet, sentiment, alternatives.
PM playbook
Adoption angles, user fit, positioning.
CEO playbook
Traction signals, ROI, build vs buy.
Deep-dive insight
Full long-form analysis, no fluff.
Easy mode
Core idea, fast — when you need the gist.
Pro mode
Technical nuance, edge cases, tradeoffs.
Read the full digest
Go beyond the preview

Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.

Underrated tools. Unfiltered takes.

Read the full digest in the Snaplyze app for deep-dive insight, Easy and Pro modes, and the playbooks you can actually use.

Install Snaplyze →