TL;DR
LBTC is a yield-bearing claim on Bitcoin. Since the October report, the admin structure has stayed the same, the contracts have changed, and the yield engine has gone quiet.
The admin structure has not changed. The token's upgrade authority is still a 24-hour Timelock A built-in delay between an admin approving a change and the change taking effect, so users can withdraw first if they disagree.. The only executor is a 3-of-5 Gnosis Safe of five unlabeled keys.
On 2026-10-29 that Safe used the power. In one batch it upgraded LBTC, BTC.b, the Security Consortium contract and Lombard's AssetRouter. It also granted itself MANAGER_ROLE on LBTC and BTC.b. That role lets it change per-minter mint rate limits and unpause minting with no timelock. It does not let it upgrade code or mint.
Two things improved. The Safe has had a Hypernative transaction guard since 2026-10-22. And this time the Safe queued the upgrade, not the deployer EOA as in April and July.
The quiet part is the yield engine. Lombard still publishes no realized yield for the Bitwise covered-call book. Its docs still do not say whether proof of reserve covers the custodian accounts.
The Peg and depeg A stablecoin's peg is the price it targets, usually $1. A depeg is a move away from it, most often down. The stables page checks prices every 5 minutes. held. Holders are leaving: LBTC TVL Total value locked: the dollar value of everything deposited in a protocol or pool. It shows size, not safety. in BTC terms is down about 19% in five weeks. The verdict stays caution.
Checklist
Audits & contracts. The Audit A security firm's review of a protocol's code. It lowers the odds of a bug but does not rule one out, so check what was in scope. folder in Lombard's contracts repo has not changed since 2026-07-09. It holds 19 reports and a README, from Halborn, OpenZeppelin, Veridise, Sherlock and ABDK. The repo's last public commit is 2026-08-05.
On 2026-10-29 four contracts got new code:
- LBTC now runs an implementation verified on Blockscout as
StakedLBTCon 2026-09-03. - BTC.b runs
NativeLBTC. - The consortium contract runs
Consortium. - The AssetRouter proxy 0x9ece5fb1 runs
AssetRouter.
The LBTC code includes setMinterLimit, which fits the June and July 2026 mint-limit audits by name. We did not match the deployed bytecode to an audited commit (not verified in this review).
On 2026-11-05 the Safe configured a new contract named "Bitcoin DEX LP (liquidity provider) Depositing two tokens into a trading pool to earn its swap fees. If their prices drift apart, you end up holding more of the one that fell. Strategy" (symbol BTClp). Its implementation is verified as MultiAssetWithAsyncRedemptionStrategy, and it references LBTC, BTC.b and cbBTC. The folder holds June 2026 "strategies" audits from OpenZeppelin and Veridise. We did not confirm that they cover this contract, and we found no documentation of what it does (not verified in this review). Yellow.
Admin control. This dimension sets the verdict, and it stays red. We re-read it on 2026-11-07 at Ethereum block 26,363,259.
- The EIP-1967 admin slot still points to ProxyAdmin 0xbAE061c7. Its owner() and LBTC's owner() both return timelock 0x055E84e7. LBTC's defaultAdmin() is the same timelock.
- getMinDelay() returns 86,400 seconds.
- The Safe at 0x251a604e holds PROPOSER, EXECUTOR and CANCELLER. Its threshold is 3, and its five owners are the same plain EOAs as in October. Its nonce has moved from 185 to 192.
- The deployer EOA 0x3f6bf1c3 still holds PROPOSER.
- The consortium contract holds no role, and address(0) is not an executor.
- The ProxyAdmins behind BTC.b, the consortium, the AssetRouter and the exchange-rate Oracle The price feed a protocol trusts to value collateral. A wrong or manipulated price can cause unfair liquidations or let bad loans through. are owned by the same timelock.
What happened since 2 October:
- 2026-10-22: the Safe set a transaction guard. Blockscout names its verified source
HypernativeGuard. We did not read the guard's policy. - 2026-10-23: the Safe queued a six-call batch on the timelock. Four calls were upgradeAndCall: LBTC to 0xe15382bc, the consortium 0xdAD58DfA to 0xed43b662, BTC.b to 0x1b53b627, and AssetRouter 0x9ece5fb1 to 0x8c5f1379. The other two granted the Safe MANAGER_ROLE on LBTC and on BTC.b.
- 2026-10-28: the Safe queued a rename of LBTC to "Lombard BTC". On 2026-11-07, name() still returns "Lombard Staked Bitcoin", so the rename had not executed.
- 2026-10-29: the Safe executed the batch. In the same transaction it called setMinterLimit directly, which we decoded against the verified ABI. Per 4 days: 400 BTC for the AssetRouter on LBTC and BTC.b, and 400 BTC for BTC.b's own address on BTC.b. Per 2 days: 300 BTC for the BridgeV2 proxy 0x451c5498 on both tokens.
In the verified LBTC source, MANAGER_ROLE gates two functions: setMinterLimit and unpauseMintBurn. So three of the five keys can now raise or lower these mint caps at once, with no 24-hour window. Those caps are a brake on minting, not a way to mint.
The timelock's own transaction list has no direct schedule() call since 2026-07-01. So unlike April and July, the deployer key did not queue this upgrade.
None of this changes the core problem. Three of five anonymous keys can replace the code of a token backed by several thousand BTC. Holders get 24 hours' notice, and we know of no public alert that a change is queued. The guard is a real improvement, but its rules are not public.
Oracle. There is no market-price oracle in the mint path, but there is a rate oracle in the redeem path. LBTC's getRate() reads 1.00549 (BTC per LBTC), the same value as contract 0x1De9fcfe. Blockscout names that contract's implementation StakedLBTCOracle. Its token() is LBTC. It accepts new ratios only with a consortium proof, within a threshold its owner sets. That owner is the 24-hour timelock, which can also upgrade it. The deployer EOA queued its most recent upgrade, on 2026-07-01.
Lombard's oracle docs, updated 2026-11-02, list this same contract as their EVM proof-of-reserve contract. They say the system "operates independently of Lombard". It monitors "Bitcoin addresses controlled by the protocol", compares them with LBTC and BTC.b supply across chains, and publishes every 10 minutes. Chainlink and RedStone both run LBTC price feeds on Ethereum for integrations.
The yield-strategy page says strategy metrics are "attested by the strategy manager, Bitwise, and cross-checked against custodial records". It also says the proof-of-reserve attestations verify the backing "independent of the manager". Neither page names the Anchorage or Kraken accounts as proof-of-reserve inputs. Anchorage's own write-up describes the custody structure without mentioning reserve attestations. Whether the custodial 50 to 60% is read independently remains not verified in this review. Yellow.
Liquidity & exit. Docs updated 2026-11-02 say redemptions settle in native BTC "within a window of up to 10 days". They say "there is no gate or pause mechanism, but redemption is not instant", and that the passive allocation funds redemptions first.
The contract is less absolute than the docs:
- PAUSER_ROLE on LBTC is held by a separate Safe, 0xad67ba27, with a 2-of-11 threshold. Four of the admin Safe's five owners are among its signers.
- That Safe can pause transfers. Only DEFAULT_ADMIN, which is the 24-hour timelock, can unpause them.
- The same timelock can switch off BTC redemptions through toggleRedeemsForBtc.
- Today redemptions are enabled, mint and burn are not paused, and paused() is false.
A fast pause is a sensible defence against an exploit. It also means a small group can freeze LBTC, and an unfreeze takes at least a day. We found no published rule for a Cooldown and withdrawal queue The wait between asking to withdraw and getting your funds: a fixed cooldown (7 days for HYPE staking) or a queue that clears as cash comes back. larger than the passive slice (not verified in this review).
On the secondary market we took 74 DeFiLlama samples from 2026-10-01 to 2026-11-07. They were taken twice a day, around 00:00 and 12:00 UTC, with LBTC paired to BTC within 15 minutes. They ranged from 0.99816 (2026-11-05, about 23:57 UTC) to 1.00408 (2026-10-08), and none was below 0.995. The low is a little deeper than September's 0.99967. Both samples on the upgrade day, 2026-10-29, were above 1.001.
Measured against LBTC's own redemption rate of 1.00549, though, the market spot ratio on 2026-11-07 (1.0014) sits about 0.4% lower. We did not check how DeFiLlama prices LBTC (not verified in this review). Yellow.
Yield: real vs emission. The yield-strategy page, updated 2026-11-02, gives these terms:
- The active allocation targets 50 to 60% of backing, with a 60% cap. It sits in segregated, Lombard-owned accounts at Anchorage Digital Bank and Kraken Institutional.
- Bitwise Investment Manager, LLC holds "discretionary trading authority only" and cannot withdraw, transfer or rehypothecate the BTC.
- The target is 2.5% net APY Yearly yield with the earnings reinvested (compound interest). Most tables here show APY; funding and the exchange vaults show APR. in BTC terms, after a 20% protocol rewards fee. The page calls it "a target, not a guarantee".
The options are financially settled, and the page says "no Bitcoin changes hands at expiry". If BTC nears a strike, the position is bought back and rewritten higher. For a sharp rally the page describes "a controlled cost to reset" and a "temporary mark-to-market drawdown". That changes how a loss shows up, not whether one can happen. The page also names counterparty risk on OTC options positions.
The claim that no short option has expired in the money since 2022 refers to the covered-call strategy's own 4.5-year operating history. That history predates LBTC's allocation, which began in August 2026. We still found no realized-yield figure, and no confirmation that the allocation has reached 50 to 60% (not verified in this review). The yield is premium income, not Emissions and points Emissions are new tokens a protocol issues to pay rewards; they count in the reward yield. Points may turn into tokens later and are never counted in a rate.. BARD trades at about $0.111, down from $0.1427 on 2026-10-02. Yellow.
Holder concentration. We pulled the distribution this run, for Ethereum only, from Blockscout's top holders:
- Supply is 6,413.76 LBTC across 22,965 holders.
- Aave's aEthLBTC holds 2,565.04 (40.0%) and Spark's LBTC market holds 1,136.59 (17.7%).
- A third contract, 0x087cbB1a, holds 582.01 (9.1%). Its proxy type (
MigratableEntityProxy) matches Symbiotic Vault and curator A shared deposit pool run by code or by a curator. The curator chooses which markets get your money and sets the limits, for a fee., but the label is not confirmed. - The top 15 addresses hold 89.7%.
About 58% of Ethereum LBTC therefore sits as collateral in two lending markets. A sharp discount would flow straight into Liquidation When a loan passes its LLTV or a perp position runs out of margin, it is closed by force and the collateral is sold, usually with a penalty. there. On the backing side, half or more sits with two custodians under one trading manager. Yellow.
Track record. We checked X via Grok, web sources and DeFiLlama's hacks list (current to 2026-11-05) for 2026-10-02 to 2026-11-07. None showed an exploit, depeg, paused redemption or reserve challenge for Lombard. LBTC paused() reads false.
X chatter about an "L-BTC exploit" in this window concerns Blockstream's Liquid Network L-BTC, a different asset. The only Lombard-related entry in DeFiLlama's hacks list is still the February 2025 Ionic loss, which came from a counterfeit LBTC contract.
Two things keep this dimension yellow. The custody and yield model is under three months old. And outflows have sped up:
- The LBTC child TVL was about 8,455 BTC on 2026-10-01 and about 6,885 BTC on 2026-11-07, down 18.6%.
- Ethereum supply fell from 7,644.54 to 6,413.76, down 16.1%.
Worst case
The cheapest path to harming holders is still the upgrade path. Three of the five Safe keys queue a malicious implementation, and it lands 24 hours later. This month showed the path works end to end: on 2026-10-29 the same keys rewrote LBTC, BTC.b, the consortium and the AssetRouter in one batch.
The same timelock also owns the oracle that sets LBTC's redemption rate. The Hypernative guard may block an obviously hostile transaction. Its rules are not public, and the Safe's own signers set it.
A second path needs no code. A freeze, legal hold or operational failure at Anchorage or Kraken Institutional could affect up to 60% of the backing at once. The consortium's multi-party signing does not protect that share. Release from the Anchorage tri-party structure needs Lombard, the manager and Anchorage to agree. That guards against theft but also slows recovery.
The likelier bad day is quieter. BTC rallies hard, and rolling the short calls costs the active book BTC. Outflows keep running at this month's pace, and the redemption queue leans on the passive slice. If the 2-of-11 pauser Safe freezes transfers in a scare, they stay frozen for at least the 24-hour timelock. Until then the only fast exit is selling LBTC on the market. No insurance fund covers any of these cases. Position sizing is the mitigation.
Bottom line
Caution. The admin red is unchanged in substance. Three of five anonymous keys decide what LBTC's code is. They exercised that power on 2026-10-29 with code we could not tie to a published audit, and they now set mint rate limits with no timelock.
Two things are better than in October: the Safe has a transaction guard, and the deployer EOA stood aside this time. Two are no clearer: Lombard still publishes no realized yield, and no statement that proof of reserve reads the custodian accounts. The peg held, but holders are leaving in BTC terms. Hold LBTC only in a size you could leave locked for ten days, or lose.
Data appendix
- TVL and scope: This report covers LBTC and uses DeFiLlama's LBTC child figure.
- DeFiLlama parent
parent#lombard-financewas about $751.8M on 2026-11-07 at about 13:15 UTC. It splits intolombard-lbtc$521.74M, Lombard BTC.b $160.73M and Lombard Vaults $69.37M. - LBTC child history: $706.67M on 2026-10-01, $684.92M on 2026-10-02, $639.84M on 2026-10-15, $549.27M on 2026-11-01 and $521.74M on 2026-11-07. DeFiLlama counts all of it on the Bitcoin chain.
- In BTC terms, using DeFiLlama BTC at about $75,782: the LBTC child is about 6,885 BTC, against about 8,455 on 2026-10-01 (down 18.6%). The parent is about 9,920 BTC, against about 11,418 on 2026-10-01 (down 13.1%).
- DeFiLlama parent
- Supply (on-chain, block 26,363,259): Ethereum LBTC totalSupply is 6,413.76481631 LBTC (8 decimals), down from 7,644.54 on 2026-10-02 and 8,443.38 on 2026-08-12. Ethereum BTC.b (0xb0f70c0b) supply is 107.92. Supply on other chains was not summed (not verified in this review).
- On-chain control path (read 2026-11-07):
- LBTC 0x8236a87084f8B84306f72007F36F2618A5634494.
- Admin: ProxyAdmin 0xbae061c73876952aa2c5e483b74dfa785425f879, whose owner() is timelock 0x055e84e7fe8955e2781010b866f10ef6e1e77e59. LBTC's owner() and defaultAdmin() are the same timelock, and the timelock holds DEFAULT_ADMIN_ROLE on LBTC.
- ProxyAdmins 0xbf4202c8 (AssetRouter), 0x1629ae77 (consortium), 0xcee83a2b (BTC.b) and 0xe6c176a0 (oracle) are all owned by the same timelock.
- Implementation: 0xe15382bc6968a50c5ff5af193d03de6be4d0270f, verified on Blockscout as
StakedLBTCon 2026-09-03. It was 0x07207231 on 2026-10-02. - getMinDelay() = 86,400s.
- Timelock roles: Safe 0x251a604e8e8f6906d60f8dedc5aaeb8cd38f4892 holds PROPOSER, EXECUTOR and CANCELLER. Deployer 0x3f6bf1c36ccbb59eaf8415301a0cec73c344a079 holds PROPOSER only. The consortium 0xdAD58DfA and address(0) hold none.
- MANAGER_ROLE (keccak256("MANAGER_ROLE") = 0x241ecf16) on LBTC and BTC.b: the Safe yes, the deployer no. In the verified source it gates setMinterLimit and unpauseMintBurn.
- PAUSER_ROLE on LBTC: Safe 0xad67ba2795770c8e0b70e2896c0f81f9d313fd44 (threshold 2 of 11 owners), granted at block 24,950,539. unpauseTransfers and toggleRedeemsForBtc require DEFAULT_ADMIN (the timelock).
- MINT_BURN_PAUSER_ROLE: we found no RoleGranted event, so no holder was identified (not verified in this review).
- State: isRedeemsEnabled() true, mintBurnPaused() false, paused() false.
- Admin Safe: threshold 3. Owners 0xd7b78bf1, 0x11674409, 0x70b9b04b, 0xd775959e and 0xdd48b7cf all have no contract code. Nonce 192. Guard 0x87bde523e05fee2c557d6f592f7eb686c69189ab (
HypernativeGuardon Blockscout). - Caveat: the timelock is not enumerable, so this confirms which addresses hold roles, not that no other address does.
- Safe activity since 2026-10-02 (Etherscan; all are execTransaction calls sent by relayer 0x56497480):
- 2026-10-22 18:18 UTC: setGuard to HypernativeGuard.
- 2026-10-23 13:21 UTC: timelock scheduleBatch, delay 86,400s. Four upgradeAndCall calls (AssetRouter 0x9ece5fb1 to 0x8c5f1379
AssetRouter, consortium to 0xed43b662Consortium, BTC.b to 0x1b53b627NativeLBTC, LBTC to 0xe15382bcStakedLBTC) and two grantRole(MANAGER_ROLE, Safe) calls on LBTC and BTC.b. - 2026-10-26 09:40 UTC: a call to the guard, selector 0x395c91fe; not decoded.
- 2026-10-28 18:56 UTC: timelock schedule of LBTC changeNameAndSymbol("Lombard BTC", "LBTC"). Not executed as of 2026-11-07, since name() is still "Lombard Staked Bitcoin".
- 2026-10-29 10:12 UTC: a MultiSend that ran executeBatch of the 23 October batch, then five setMinterLimit(address,(uint96,uint32)) calls (selector 0x98a5470a).
- On LBTC: AssetRouter 400 BTC per 345,600s, and BridgeV2 0x451c5498 300 BTC per 172,800s.
- On BTC.b: the same two limits, plus 400 BTC per 345,600s for 0xb0f70c0b (BTC.b's own address).
- 2026-11-05 12:04 UTC: role grants and configuration on 0x5089fd06. Its name() is "Bitcoin DEX LP Strategy", its symbol BTClp, and its implementation 0x88cCd4b5 is verified as
MultiAssetWithAsyncRedemptionStrategy. The setup references LBTC, BTC.b and cbBTC. - 2026-11-05 12:04 and 12:07 UTC: calls to the BlocklistOracle proxy 0xc94b1e74. Not decoded. Purpose: not verified in this review.
- The timelock has no direct transactions since its 2026-07-01 schedule() call.
- Exchange-rate oracle: 0x1De9fcfeDF3E51266c188ee422fbA1c7860DA0eF, implementation 0x4757a83e (
StakedLBTCOracle).- token() is LBTC, and owner() is the timelock.
- getRate() is 1.00549, equal to LBTC getRate(). The ratio is published by consortium proof.
- Lombard docs list it as the EVM proof-of-reserve contract.
- Custody and yield model: Lombard docs
/use/lbtc/yield-strategy, last updated 2026-11-02.- Allocation: active target 50 to 60% (maximum 60%) at Anchorage Digital Bank and Kraken Institutional, under a tri-party agreement in bankruptcy-remote accounts. Passive 40 to 50% in Security Consortium custody.
- Manager: Bitwise, with discretionary trading authority only.
- Yield: 2.5% net target after a 20% fee. Options are financially settled, rolled before strike, and traded as OTC positions with counterparty risk. The dashboard refreshes every 24 hours.
- Realized yield: not published (not verified in this review).
- The Anchorage insight page (byline 2026-08-13, page metadata 2026-09-17) describes the custody structure and does not mention reserve attestations.
- Audits: github.com/lombard-finance/evm-smart-contracts/docs/audit holds 19 PDFs plus a README.
- The last folder commit was 2026-07-09; the last repo commit was 2026-08-05.
- Newest by name: OZ_mintlimit_07_26, Sherlock_mintlimit_06_26, OZ_strategies_06_26 and Veridise_strategies_06_26.
- PDF contents were not read.
- Audit coverage of the 2026-10-29 implementations and of the DEX LP strategy: not verified in this review. Immunefi bounty: not verified in this review.
- Oracle / proof of reserve: Docs
/learn/transparency/oracles, updated 2026-11-02, describe protocol-controlled BTC addresses, compared with LBTC and BTC.b supply every 10 minutes.- The base address list contract is 0xe7Ebc588 on Base.
- Listed PoR contracts: Lombard 0x1De9fcfe (EVM), RedStone 0xb415eAA3 (Ethereum).
- Price feeds on Ethereum: Chainlink 0x5c29868C and RedStone 0xb415eAA3.
- Custodian accounts are not mentioned. Whether proof of reserve covers them: not verified in this review.
- Peg: DeFiLlama coins chart, 74 samples from 2026-10-01 to 2026-11-07, at about 00:00 and 12:00 UTC daily, each matched to BTC within 15 minutes.
- Range: 0.99816 (2026-11-05, about 23:57 UTC) to 1.00408 (2026-10-08). None below 0.995.
- Spot 2026-11-07: LBTC $75,894.71, BTC $75,788.15, ratio 1.0014, against an on-chain rate of 1.00549.
- Holder concentration (Ethereum, Blockscout): 22,965 holders.
- Aave aEthLBTC 0x65906988: 40.0%. Spark LBTC 0xa9d4EcEB: 17.7%.
MigratableEntityProxy0x087cbB1a: 9.1%. - Unlabeled EOA 0x14ce84B7: 7.8%. Unlabeled EOA 0xb213531a: 4.4%.
- Top 15: 89.7%.
- Other chains: not verified in this review.
- Aave aEthLBTC 0x65906988: 40.0%. Spark LBTC 0xa9d4EcEB: 17.7%.
- Token: BARD about $0.111 (DeFiLlama, 2026-11-07). Unlocks: not verified in this review.
- Recent news scan (2026-10-02 to 2026-11-07): no Lombard exploit, depeg, paused redemption or reserve challenge found.
- Sources: X via Grok, web sources, and DeFiLlama's hacks list (current to 2026-11-05).
- The L-BTC exploit chatter in this window concerns Blockstream's Liquid L-BTC.
- Lombard blog post in the window: the Lombard App via Ledger Wallet (2026-10-06). Maintained monthly. Methodology: DeFi Research Instruction v2.