Aave assessment identifies pooled BTC.b/LBTC custody ahead of proposed V4 onboarding

What happened

LlamaRisk published an official Aave risk assessment conditionally supporting BTC.b onboarding to the Aave V4 Core Hub on Ethereum while identifying that BTC.b and LBTC reserves are currently pooled rather than economically segregated.

What changed

The assessment adds material evidence that the existing proof-of-reserve view does not map dedicated reserves to BTC.b, that an LBTC operational shortfall could therefore affect backing available to BTC.b holders, and that nearly all Ethereum DEX liquidity is supplied by Lombard. It also reports the Ethereum Bascule check was enabled on September 1, 2026.

What did not change

No Aave onboarding execution is established. The assessment reports aggregate Lombard reserves sufficient for identified BTC.b and LBTC issuance and does not identify a depeg, unbacked mint, reserve shortfall, exploit, or change to the 10-of-14 consortium threshold.

Confirmed

• The assessment supports Aave V4 onboarding only on the condition that BTC.b and LBTC custody be segregated.
• The assessment observes pooled custody across BTC.b and LBTC and says current proof-of-reserve data does not establish asset-level segregation.
• The assessment calculates aggregate reserves as sufficient for identified BTC.b and LBTC issuance, with an indicated 18.54 BTC excess.
• BTC.b upgrades are subject to a one-day timelock whose executor is a Lombard-controlled 3-of-5 Safe.
• The Ethereum Bascule check was enabled on September 1, 2026.
• The assessment reports approximately $7.9 million of Ethereum DEX liquidity, nearly all supplied by Lombard.

Still open

• Whether Lombard completes the reported per-asset custody segregation and publishes verifiable address-level mapping.
• Whether Aave governance approves and executes BTC.b onboarding to the V4 Core Hub.
• Whether the assessment's reported BTC.b native-redemption timing of roughly one hour median remains reliable under stress.
• How quickly Ethereum liquidity could deteriorate if the Lombard-supplied position is withdrawn.
• Whether pooled custody changes the existing memo's approved-with-limits conclusion or sizing constraints.

What it means for an advisor

• Reconcile the existing BTC.b memo because its custody and redemption interpretation may not reflect the newly documented pooled reserve structure and asset-specific exit observations.
• Treat BTC.b and LBTC as economically interdependent until dedicated BTC.b reserve segregation is implemented and independently verifiable.
• Do not infer that conditional risk-provider support constitutes Aave governance approval, live onboarding, or advisor approval.
• Reassess liquidity assumptions because the principal Ethereum pool depends almost entirely on a protocol-aligned supplier.

Previous interpretation

The Lombard BTC.b memo described segregated backing and a nine-to-ten-day native-BTC redemption path; the new assessment instead describes pooled BTC.b/LBTC custody and reports substantially shorter BTC.b redemption observations, requiring reconciliation before continued reliance.