Bedrock uniBTC

Our research supports rejecting uniBTC for this advisor sleeve. It adds an upgradeable, multichain liquid-restaking wrapper to Bitcoin custody and has already suffered the exact minting risk that wrapper holders bear. In September 2024, an externally callable vault path treated ETH as native BTC and minted 30.8 unbacked uniBTC, causing roughly $2M of DEX-liquidity loss across a vulnerability deployed on eight chains. Later audits and Chainlink Proof of Reserve/Secure Mint controls are meaningful fixes, but they do not justify replacing native BTC with a restaking and bridge claim.

Review triggers: events that reopen the verdict
• uniBTC completes 24 consecutive months without a mint, reserve, bridge, or redemption incident after Secure Mint deployment
• Independent attestations reconcile every uniBTC liability by chain to reserves and disclose all custodians and encumbrances
• A proposed-size conversion to native BTC completes within a published service level under stressed secondary liquidity
• Any reserve-feed bypass, unbacked mint, bridge compromise, or redemption pause opens an immediate review

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-19.

The research file

Mechanism and client claim

Bedrock accepts supported Bitcoin representations and issues uniBTC, a transferable token intended to retain BTC exposure while participating in Babylon-linked staking and DeFi. The token and vault contracts are deployed across many EVM and Bitcoin-adjacent chains, so custody, minting, reserve accounting, bridging, and each chain’s token contract all sit between the holder and the original Bitcoin. Chainlink Proof of Reserve and Secure Mint now gate issuance against reported reserves, but an oracle-mediated reserve check is an additional control dependency rather than native Bitcoin settlement.

Control, governance, and legal perimeter

Bedrock publishes contract addresses, audits, proof-of-reserve integration and a team-operated product surface. Vault and token implementations remain upgradeable or administratively controllable across deployments, and the issuer chooses accepted collateral, staking integrations, chain expansion, pausing, and remediation. Proof of Reserve constrains minting only to the extent the monitored addresses, feed configuration, and secure-mint integration cover every liability. A multichain token also inherits bridges and remote-chain administrators; the same ticker cannot be treated as one identical control object everywhere.

Incident and operating record

Bedrock’s own post-mortem says the 2024 vulnerability allowed 30.8 uniBTC to be minted and exchanged for WBTC, affected about $2M of liquidity, existed on eight chains, and involved 125 exploiters; reserves remained secure and the vulnerable contract was paused and fixed. Dedaub reports it discovered and disclosed the issue before exploitation but could not reach the team for roughly two hours, after which attackers acted. Bedrock subsequently published new BlockSec and PeckShield reports. Remediation improves the current design, but a realized infinite-mint class failure weighs more heavily than a later audit count.

Exit, liquidity, and failure path

A holder can seek protocol conversion where supported or sell uniBTC through secondary liquidity. Neither path is equivalent to spending native BTC: conversion depends on the accepted reserve asset, vault state, chain, bridge, operator process, and any staking or unbonding constraint, while market sale can discount during a reserve or minting scare. The 2024 exploit specifically monetized unbacked units against LP reserves, demonstrating how secondary exit providers absorb wrapper failure before reserve holders necessarily lose custody assets.

Comparison and decision

Native BTC avoids issuer, vault, oracle, bridge, restaking, and remote-chain risks. tBTC supplies a more explicitly decentralized threshold-custody alternative when Ethereum composability is genuinely required, though it too remains rejected absent a specific approved use. uniBTC’s added yield or points do not compensate a mass-affluent diversification sleeve for a previously realized mint-control failure. Reopen requires a narrowly approved use, long post-remediation record, liability-level reserve reconciliation, and tested native redemption, not merely a higher APY or TVL.

Sources

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

• Bedrock — uniBTC contracts · primary · accessed 2026-08-19
  Supports: contract addresses, multichain deployments, vaults
• Bedrock — audit reports · primary · accessed 2026-08-19
  Supports: BlockSec audits, PeckShield audits, audit dates
• Bedrock — Chainlink Secure Mint integration · primary · accessed 2026-08-19
  Supports: Proof of Reserve, Secure Mint, reserve gating
• Bedrock — uniBTC incident post-mortem · primary · accessed 2026-08-19
  Supports: 30.8 uniBTC mint, $2M liquidity impact, eight chains, response
• Dedaub — Bedrock vulnerability disclosure · secondary · accessed 2026-08-19
  Supports: disclosure timeline, infinite-mint root cause, $1.8M loss estimate
• DefiLlama — Bedrock uniBTC protocol data · secondary · accessed 2026-08-19
  Supports: protocol category, chain perimeter, current TVL

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.