Lombard BTC.b

The scheduled date is the outside bound. Kill criteria are checked every day, and a trigger reopens the memo that week.

APPROVED WITH LIMITS, THE STRONGEST-GOVERNED BITCOIN WRAPPER 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 — validates every mint, redemption, and cross-chain transfer under a 10-of-14 threshold, with the protocol defaulting to a pause, not a proceed, if quorum cannot be reached. That is a materially broader, more transparent approval set 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 — nine to ten days through Babylon unbonding plus Lombard’s rebalancing cycle — a real, disclosed liquidity constraint this cap prices rather than a concealed one.

Kill criteria: the events that revoke this 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

The research file

Mechanism

Lombard issues two related products from the same custody stack: LBTC, which is yield-bearing through covered-call options managed by Bitwise Investment Manager, and BTC.b, 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 the token mints automatically on the destination chain. Backing splits 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, in segregated, Lombard-owned accounts; Bitwise holds trading authority for the LBTC strategy only, never custody.

Control and governance

A 14-member Security Consortium, including named institutions such as Galaxy, DCG, OKX, Wintermute, Amber, Antpool, and F2pool, validates every mint, redemption, and cross-chain transfer under a 10-of-14 threshold; Lombard states not even 9 compromised members could authorize a transaction alone. Real-time mempool anomaly detection can pause the protocol pre-emptively, and if too few members are online to reach quorum, the protocol pauses new operations by default rather than proceeding without full authorization — a fail-closed, not fail-open, design. Additional layers include hardware security modules through Cubist’s CubeSigner, Bascule Drawbridge dual-layer verification, and multi-party approval timelocks. Contracts are audited by six independent firms including OpenZeppelin, Halborn, and Veridise. In May 2026 Lombard migrated more than $1B in Bitcoin-backed assets from LayerZero to CCIP, proactively, in direct response to the April 2026 Kelp DAO/LayerZero exploit already rejected in this registry — the same proactive-migration pattern already credited toward Kraken Bitcoin’s approval.

Incident record

No LBTC or BTC.b depeg or exploit was identified since launch. The one relevant event is ecosystem-adjacent rather than a Lombard-specific failure: the April 2026 Kelp DAO exploit on LayerZero prompted the CCIP migration above. Secondary-market price can still dislocate from fair value during stress, a market-liquidity risk rather than a backing failure, since the token remains fully 1:1 backed regardless of quoted price.

Exit

Redemption for native BTC takes nine to ten days total: Babylon’s seven-day unbonding period plus Lombard’s daily rebalancing cycle, and this cannot be shortened. This is a disclosed, structurally necessary delay, not a concealed KYC gate; a holder needing faster liquidity can sell on secondary markets at prevailing price instead. This registry treats that delay as a real constraint on the cap, not as friction to wave off.

Comparison

Materially stronger-governed 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. Against SolvBTC, rejected despite comparably strong governance because of a realized March 2026 exploit, Lombard has no comparable loss event. Against Kraken Bitcoin, also approved with limits in this registry, Lombard trades KYC-gated-but-fast redemption for permissionless-but-slow redemption — both honest, disclosed tradeoffs, priced differently in each entry’s cap.

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