unionlabs/union

Choose this fork only if you want a tailored Union deployment and can absorb heavy maintenance. If you want a current, broadly supported bridge codebase, upstream is the safer choice.

Prefer this fork only if you need its custom app, Voyager, or deployment changes and are willing to own a large rebase burden. If you want the latest protocol, SDK, and compatibility work, upstream is the safer default.

Prefer this fork if your goal is a Bob-centered, deployment-oriented Union variant with custom integration work. Prefer upstream if you need the broadest, freshest, and most complete Union feature set across chains, docs, SDKs, and protocols.

Choose this fork only if its Bob-oriented changes and local deployment workflow are exactly what you need. For most adopters, upstream is the safer default because this fork is materially behind and highly divergent.

Choose this fork only if you specifically want its app2 transfer/UI and Arbitrum/Voyager direction. If you want current Union infrastructure with lower maintenance risk, upstream is the better default.

Prefer this fork only if its local UX and experimental workflow changes are the product. For anyone wanting current Union infrastructure, upstream is the safer choice because this fork is both stale and materially behind.

Choose this fork only if Bob-specific changes or the custom consensus/deployment work are the reason you are adopting it. If you want current Union capabilities, this fork is too far behind upstream to be a low-risk base.

Prefer this fork only if its added app/deployment tweaks match your exact workflow and you are prepared to absorb major upstream drift. For most adopters, upstream is the safer choice because this fork is far behind and likely missing newer protocol, SDK, and operational fixes.