UniRouter

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED ON UNRESOLVED DISCLOSURE GAPS. Despite the name, UniRouter is unrelated to Uniswap: it is a Bitcoin liquid-staking platform built on B² Network, a Bitcoin Layer 2, issuing uBTC/stBTC against BTC staked through Babylon’s Bitcoin staking protocol. No audit of any kind was found for UniRouter’s contracts, no minting-authority or signer disclosure exists for the MuSig2-aggregated custody wallet, and the protocol’s own architecture documentation does not describe unstaking or redemption mechanics at all. Absence of a reported incident is weak evidence given how thin the public documentation is.

Kill criteria: the events that revoke this verdict
• UniRouter publishes an independent, named third-party security audit covering the staking-vault and minting contracts
• MuSig2 signer or validator set composition and threshold are publicly disclosed and independently verifiable
• Redemption and unstaking mechanics, including timing and any Babylon-unbonding-period pass-through, are documented and demonstrated at proposed size
• Twelve consecutive months with no depeg, slashing-related loss, or custody incident following the above disclosures

The research file

Mechanism

BTC is locked via signature-aggregated wallets using MuSig2 aggregation. The architecture is built directly on Babylon’s Bitcoin staking protocol: UniRouter validators initiate staking transactions, and appointed node operators handle validation duties on the Babylon chain, using Babylon’s Extractable One-Time Signature slashing model, where a staker’s key becomes exposed and funds slashable if a validator equivocates. Users receive uBTC or stBTC, a staking-derivative token representing their staked value while nominally remaining liquid.

Control and governance

UniRouter’s own documentation describes ”delegated validators” and ”node operators” but does not specify MuSig2 signer thresholds, committee composition, who controls uBTC minting authority, or any pause or freeze capability. No governance token, DAO, or named multisig signers were found anywhere in the reviewed materials.

Incident record

No confirmed exploit, depeg, or security incident was identified through this review’s 2026-08-17 search cutoff. That is a bounded negative finding only: public documentation is thin enough that absence of reporting is weak evidence of an actually clean record. No audit report, firm name, or audit scope was found anywhere in the reviewed documentation or search results.

Exit

UniRouter’s own architecture documentation explicitly does not describe unstaking procedures, withdrawal timelines, or redemption mechanics for uBTC or stBTC. That is an unresolved gap this review could not close from any primary source, meaning a client’s exit path from this product cannot currently be verified at all.

Comparison

The same undisclosed-control-and-exit pattern already rejected in this registry for Lorenzo enzoBTC (unconfirmed redemption and authority) and Unit (a thin, unnamed guardian set), but thinner still: UniRouter discloses no audit of any kind, where those two at least had some third-party review referenced. Against native BTC held directly, or against Babylon staking directly, UniRouter adds an unaudited intermediary layer with no disclosed control map or exit path. Building on Babylon does not cure that gap: this registry’s own Babylon Protocol memo, researched independently, found zero registered audits for the underlying staking protocol and an undisclosed covenant-committee membership and threshold — meaning UniRouter stacks its own undisclosed validator and minting authority on top of a base layer this registry already found insufficiently disclosed in its own right, rather than inheriting a solid, already-vetted foundation.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• DefiLlama — UniRouter protocol record · secondary · accessed 2026-08-17
  Supports: protocol identity confirmation
• UniRouter — official site · primary · accessed 2026-08-17
  Supports: product overview
• UniRouter Dataroom — liquid-staking architecture · primary · accessed 2026-08-17
  Supports: mechanism, MuSig2 custody, Babylon integration
• UniRouter Dataroom — how to get uBTC on B² Network · primary · accessed 2026-08-17
  Supports: minting flow
• B² Network — UniRouter’s Bitcoin staking solution · secondary · accessed 2026-08-17
  Supports: ecosystem context

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.