A bridge whose security model is the product
Union connects blockchains for messages, asset transfers, NFTs, and decentralized finance. Its central claim is that a destination chain can verify the source chain's consensus rather than trust a third-party oracle, multisignature group, or multiparty-computation committee. Zero-knowledge proofs make that verification practical across chains with different designs. Union also implements IBC, the messaging standard best known in Cosmos, and extends the approach to Ethereum, rollups, and other ecosystems.
That distinction matters more than transaction speed or a polished transfer screen. Cross-chain systems are defined by what users must trust when the two networks disagree or an operator is compromised. Union's answer is light clients, consensus proofs, and contracts governed by the protocol. Teams evaluating it should begin with that model and the exact route they need, not the repository's star count.
The current README lists mainnet connections for Arbitrum, Babylon, Base, Berachain, Bob, BSC, Corn, Ethereum, Osmosis, Sei, Union, and Xion. It lists Sui only on testnet. This is meaningful reach, but it is not universal connectivity. Each new ecosystem needs light-client logic, contracts, relaying support, and operational work.
The repository contains an entire network
Union is a polyglot monorepo rather than one reusable library. uniond is the Cosmos SDK-based network node. galoisd generates zero-knowledge proofs. Voyager relays packets between ecosystems. Separate directories hold CosmWasm and EVM contracts, light clients, a production node supervisor, a faucet, the public app and site, and a TypeScript SDK. Rust is the largest language by GitHub's count, but Go, Solidity, and TypeScript are all essential to the product.
The cost of that scope is substantial. A wallet developer may only need the SDK and hosted infrastructure, while a new chain integration touches several subsystems. A node operator does not need the Astro site, but still lands in the same repository. Ownership, testing, and deployment boundaries must be understood before a team decides which parts to fork or run.
Nix makes the build repeatable, not small
The quickstart installs Nix, then builds targets such as uniond, Voyager, or the app from the flake. nix develop supplies Cargo, Rust, Node, Go, and other dependencies without scattering versions across the host. For contributors already using Nix, this is a clean answer to a difficult mixed-language build.
Everyone else pays an onboarding tax. The README says some components build only on Linux. On macOS it recommends an OrbStack NixOS virtual machine. Issue #5464 described Nix as a barrier for validators using hardened servers and standard Cosmos runbooks. That issue closed after a Makefile was added for uniond, improving the node path, but it does not turn the full monorepo into a conventional Go project.
The development setup also has a fresh loose end. On August 11, issue #5482 reported that Garnix had shut down while the repository still referenced it in flake.nix and displayed its badge. The last code push was July 25, so that report remained open after the latest push. Nix itself is not the problem, but teams should confirm binary caches and CI paths rather than copying the README blindly.
Voyager shows the operational ambition
Voyager is more thoughtfully designed than a simple event-watching script. It represents chain queries, submitted transactions, and packet data as states in a finite-state machine stored in Postgres. Each step runs through a transactional queue. If a relayer crashes, it can resume from persisted work, and independent messages can execute in parallel. That design directly addresses dropped packets and slow recovery, two serious failure modes in cross-chain operations.
It also means a production relayer owns Postgres, workers, chain RPCs, transaction keys, fees, monitoring, and the failure behavior of every connected network. L2 clients add settlement rules involving both the rollup and its parent chain. A proof can be correct while an RPC is unavailable or a transaction remains uneconomical. Union provides architecture for this work, but operators still need chain-specific runbooks and alerts.
The node has its own maturity caveat. The uniond README says Union mainnet temporarily uses proof of authority during incubation and is intended to migrate to proof of stake. That is an explicit current state, not a reason to dismiss the protocol, but validators and applications should judge the system they can use now rather than the later governance destination.
Documentation and project health
The top-level README is a good map. It explains the trust claim, component boundaries, build system, supported networks, and documentation links without pretending that one command operates the network. The Voyager architecture note is unusually useful because it explains why Postgres and the state machine exist. The TypeScript SDK README is weaker for adopters: it covers building, publishing, tests, ABI updates, and an example command, but not a friendly API walkthrough. Official hosted documentation is therefore part of the practical package.
Union's release history needs careful reading. The latest stable mainnet bundle is version 1.2.3 from January 26, 2026, but Union published 1.3.0 release candidates for the node and testnet bundle through June. Code was pushed on July 25, and a new infrastructure issue appeared in August. That combination shows ongoing work even though the latest stable tag is older. The repository's 191 open count combines issues and pull requests, while its much larger historical issue record reflects a busy monorepo rather than 191 confirmed protocol defects.
Union is a credible choice for teams that value verifiable cross-chain state enough to accept a demanding stack. Start with the supported route, read its light-client and contract implementation, and test relaying under RPC and restart failures. If your application only needs a standard Cosmos connection or a managed bridge, narrower alternatives will cost less to operate. If the bridge trust model is a first-order requirement, Union is one of the projects worth doing the harder diligence on.