Lombard BTC.b

Approved for: BTC.B on Ethereum. The limits are in the memo below.

We approve Lombard BTC.b with conditions as the Bitcoin wrapper with the strongest governance researched in this backlog. BTC.b is Lombard’s non-yield, 1:1 Bitcoin representation, backed through a Sub Custodial Trust split between decentralized Security Consortium custody and qualified institutional custodians. A named 14-member Security Consortium, including Galaxy, DCG, OKX, and Wintermute, checks every mint, redemption, and cross-chain transfer under a 10-of-14 threshold. If the group cannot reach quorum, the protocol pauses instead of proceeding. That is a much broader, more transparent approval group than every other Bitcoin wrapper reviewed in this registry, including WBTC’s 2-of-3 multisig and Function FBTC’s unconfirmed three-party council, both rejected. Redemption is slow by design, taking nine to ten days through Babylon unbonding plus Lombard’s rebalancing cycle. The advisor must assess this real, disclosed liquidity limit rather than treat it as hidden.

Review triggers: events that reopen the verdict
• Any confirmed depeg, unbacked mint, or reserve shortfall for LBTC or BTC.b specifically
• The Security Consortium threshold or named membership changes materially without public disclosure
• A confirmed compromise of the CCIP migration path, Bascule Drawbridge, or CubeSigner HSM layer affecting Lombard specifically
• The nine-to-ten-day redemption window is demonstrated to extend materially beyond its stated terms under stress conditions

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-17.

The research file

Mechanism

Lombard issues two related products from the same custody system. LBTC earns yield through covered-call options managed by Bitwise Investment Manager. BTC.b is a non-yield 1:1 Bitcoin representation with no attached strategy. A user deposits native BTC to a unique address, waits six confirmations, roughly 40 to 60 minutes, and receives the token automatically on the destination chain. Backing is split between a passive allocation, 40 to 50% of the total, held in the Security Consortium’s own decentralized custody, and an active portion held at qualified custodians including Kraken Institutional and Anchorage Digital Bank. These assets sit in segregated, Lombard-owned accounts. Bitwise has trading authority for the LBTC strategy only and never holds custody.

Control and governance

A 14-member Security Consortium includes named institutions such as Galaxy, DCG, OKX, Wintermute, Amber, Antpool, and F2pool. It checks every mint, redemption, and cross-chain transfer under a 10-of-14 threshold. Lombard says not even 9 compromised members could authorize a transaction alone. Real-time mempool anomaly detection can pause the protocol before a transaction completes. If too few members are online to reach quorum, the protocol pauses new operations by default rather than proceeding without full approval. The system therefore fails closed, not open. Other safeguards include hardware security modules through Cubist’s CubeSigner, Bascule Drawbridge dual-layer verification, and multi-party approval timelocks. Six independent firms, including OpenZeppelin, Halborn, and Veridise, have audited the contracts. In May 2026, Lombard moved more than $1B in Bitcoin-backed assets from LayerZero to CCIP. It acted in direct response to the April 2026 Kelp DAO/LayerZero exploit already rejected in this registry. This is the same early-migration pattern already counted in favor of Kraken Bitcoin’s approval.

Incident record

We found no LBTC or BTC.b depeg or exploit since launch. The one relevant event affected the surrounding system rather than Lombard itself: the April 2026 Kelp DAO exploit on LayerZero prompted the CCIP migration described above. During stress, the secondary-market price can still move away from fair value. That is a market-liquidity risk rather than a failure of the backing, since the token remains fully 1:1 backed regardless of its quoted price.

Exit

Redemption for native BTC takes nine to ten days in total: Babylon’s seven-day unbonding period plus Lombard’s daily rebalancing cycle. This delay cannot be shortened. It is a disclosed delay required by the structure, not a hidden KYC gate. A holder who needs faster liquidity can instead sell on secondary markets at the prevailing price. This registry treats the delay as a real limit that varies by client, not as minor friction to dismiss.

Comparison

Lombard has much stronger governance than every Bitcoin wrapper already rejected in this registry. WBTC’s 2-of-3 custody, FBTC’s unconfirmed council threshold, Lorenzo enzoBTC’s undisclosed authority, and Merlin’s Seal’s two-party MPC gate are all thinner and less transparent than a named 10-of-14 institutional quorum with an automatic fail-safe pause. SolvBTC was rejected despite comparably strong governance because it suffered a real exploit in March 2026. Lombard has no comparable loss event. Kraken Bitcoin is also approved with limits in this registry. Lombard replaces KYC-gated-but-fast redemption with permissionless-but-slow redemption. Both are honest, disclosed tradeoffs, and each entry’s cap prices them differently.

Sources

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

• Lombard Finance — LBTC and BTC.b integrations · primary · accessed 2026-08-17
  Supports: product overview
• Lombard Docs — BTC.b (bridged Bitcoin) · primary · accessed 2026-08-17
  Supports: mechanism, non-yield product distinction
• Lombard Finance — Bitcoin security architecture and audits · primary · accessed 2026-08-17
  Supports: audit firms, security architecture
• Lombard Finance — the Lombard Security Consortium · primary · accessed 2026-08-17
  Supports: 14-member consortium, 10-of-14 threshold, named members
• Lombard Finance — LBTC security and transparency product guide · primary · accessed 2026-08-17
  Supports: custody split, fail-closed pause design
• CoinDesk — crypto firms move $4 billion in assets to Chainlink as bridge security comes under scrutiny · secondary · accessed 2026-08-17
  Supports: CCIP migration, proactive timing

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.