Lombard commits BTC.b and LBTC to an exclusive Chainlink CCIP migration
The Ledger · · Ketju Research
Affects: Lombard BTC.b (asset) · Chainlink CCIP (other)
What happened
Lombard announced that Chainlink CCIP would become the exclusive cross-chain infrastructure for LBTC and BTC.b, replacing LayerZero on Solana, Etherlink, Berachain, Corn, and TAC and deprecating LayerZero usage on Morph and Swell.
What changed
Lombard established a concrete migration perimeter and selected CCIP's Cross-Chain Token burn-and-mint model, rate limits, and optional Security Consortium attestation as its future cross-chain architecture.
What did not change
The notice did not establish that every lane had completed migration, identify all deployed token and lane addresses, or show any change to Bitcoin reserves, redemption terms, or asset backing on May 15.
Confirmed
- The official notice was published on May 15, 2026.
- Lombard said CCIP would replace LayerZero across Solana, Etherlink, Berachain, Corn, and TAC.
- Lombard said LayerZero usage on Morph and Swell would be deprecated.
- The announced design adopts CCIP's Cross-Chain Token standard and retains Lombard ownership of token contracts.
- Lombard said its Security Consortium could provide an additional transaction attestation layer.
Still open
- The chain-by-chain cutover dates and whether each announced migration completed successfully.
- The deployed token, pool, lane, rate-limit, and Security Consortium configuration for BTC.b on each supported chain.
- The user migration process for any legacy LayerZero representation and whether liquidity remained available throughout cutover.
- Whether any legacy LayerZero contracts or privileges remained active after migration.
What it means for an advisor
- Review the Lombard BTC.b memo's bridge, token-contract, rate-limit, and Security Consortium dependency map for the new CCIP architecture.
- Verify the live route and deployed addresses for each contemplated chain rather than treating the announcement as proof of completed migration.
- Review the CCIP memo for integration-specific configuration because protocol-level CCIP approval does not validate Lombard's individual lane setup.
Sources
Version 1, published . Educational research, not investment advice.