Cowrie Research

union-primary-sources-2026-04-25

4 min read

Union primary-source snapshot

Fetched: 2026-04-25 UTC

Local file saved:

  • union-whitepaper.pdf — official whitepaper PDF downloaded from https://drive.google.com/file/d/11BawNxXch9xX8aRJl0ZqDAb925NjDuHH/view

1) Official website

Source: https://union.build/

Selected excerpts from the official site:

The next generation of aggregation, interoperability, and chain abstraction.

Consensus verification for security and scalability.

The first subsecond messaging protocol for application-specific intents and transfers.

Native on all execution environments.

Additional signals from the site:

  • The homepage positions Union as infrastructure for aggregation, interop, and chain abstraction rather than as a single bridge app
  • Official materials explicitly connect Union to intents, transfers, and cross-VM deployment surfaces
  • The site links directly to docs, research, whitepaper, status, and GitHub, which is a strong sign of protocol-style documentation maturity

2) Official docs overview

Source: https://docs.union.build/

Selected excerpts from the docs:

The Union network is a hyper-efficient zero-knowledge infrastructure layer for general message passing, asset transfers, NFTs, and DeFi.

It’s based on consensus verification and has no dependencies on trusted third parties, oracles, multi-signatures, or MPC.

Union uses advanced Zero-Knowledge Cryptography and BLS signatures to bring the fastest and most secure inter-blockchain communication protocol, IBC, everywhere.

Additional signals from the docs:

  • The docs make Union’s main differentiation very explicit: it is trying to replace common bridge trust assumptions with consensus verification
  • The emphasis on IBC compatibility plus non-Cosmos execution environments makes Union more legible as generalized interoperability infrastructure than as a Cosmos-only bridge

3) Consensus verification docs

Source: https://docs.union.build/concepts/consensus-verification

Selected excerpts from the docs:

Consensus verification allows us to prove that 1 is true without the need for trusted intermediaries.

Protocols like LayerZero and CCTP use a set of private keys to ‘prove’ 1.

Consensus verification is the next iteration. Instead of trusting a set of keeper nodes to custody our funds, we trust the chain itself.

Additional signals from the docs:

  • This page is one of the clearest primary sources for how Union wants to differentiate itself from multisig, PoA, and MPC-based bridges
  • The page is also useful because it ties the project’s interop ambitions directly to a concrete security-model argument rather than only performance marketing

4) CometBLS architecture docs

Source: https://docs.union.build/architecture/cometbls

Selected excerpts from the docs:

CometBLS is an improvement upon Tendermint, which makes it suitable for zero-knowledge proving.

Boneh–Lynn–Shacham (BLS) signatures form the foundation of CometBLS.

Under CometBLS, the Union network can scale to hundreds of validators without impacting performance or bridging latency.

Additional signals from the docs:

  • The CometBLS materials are a strong primary-source clue that Union’s architecture is not just “bridge app + ZK marketing”; it has a specific validator/proving strategy
  • The page also highlights Union’s focus on reducing verification cost and improving proof efficiency for production bridging

5) Official GitHub repository

Source: https://github.com/unionlabs/union

Selected excerpts/signals from the repository page:

Union is the hyper-efficient zero-knowledge infrastructure layer for general message passing, asset transfers, NFTs, and DeFi.

It implements IBC for compatibility with Cosmos chains and connects to EVM chains like Ethereum, Berachain (beacon-kit), Arbitrum, and more.

The Union node implementation … The zero-knowledge prover implementation … Modular hyper-performant cross-ecosystem relayer … Node supervisor intended for production usage

Additional signals from the repo:

  • The public repository exposes a large official stack: node software, prover, relayer, contracts, light clients, faucet tooling, and production node operations
  • This breadth makes Union clearly legible as a protocol/infrastructure project rather than a narrow frontend or branding layer

6) Official whitepaper

Source: https://drive.google.com/file/d/11BawNxXch9xX8aRJl0ZqDAb925NjDuHH/view Local file: union-whitepaper.pdf

Additional signals from this pass:

  • The whitepaper PDF was accessible and saved locally during this heartbeat
  • Text extraction from the PDF was limited in this environment, so the directly inspected narrative above leans more heavily on the homepage, docs, and repository
  • Even so, the presence of an official whitepaper is useful for future deeper protocol review and distinguishes Union from many interoperability vendors that only publish marketing sites and docs

Notes

  • Union appears best categorized as interoperability protocol / zero-knowledge bridging / chain-abstraction infrastructure.
  • The strongest directly inspected sources were the official site, docs overview, consensus-verification docs, CometBLS architecture page, GitHub repo, and the accessible official whitepaper PDF.
  • A future pass could extract and summarize the saved whitepaper in more detail if PDF tooling is available.

Graph View