Bridging
Move your Bitcoin assets across blockchains. Lombard uses Chainlink CCIP for secure cross-chain transfers, with an additional economic guarantee layer powered by Symbiotic.
Lombard Assets
Lombard operates two Bitcoin assets, each available on multiple chains:
LBTC
Yield-bearing BTC
Yes (Babylon staking)
DeFi, long-term holding
BTC.b
Bridged BTC
No
DeFi, trading, flexibility
Both assets are backed 1:1 by native Bitcoin and secured by the same Security Consortium.
Supported Chains
LBTC
LBTC is available on 15+ chains:
Native with Chainlink CCIP (dual-layer security):
Ethereum
Native
Base
Native
Arbitrum
Native
BNB Chain
Native
Sonic
Native
Sui
Native
Additional Chains:
Solana
LayerZero
Berachain
Native
Scroll
Lock & Mint
Mantle
Lock & Mint
Linea
Lock & Mint
Mode
Canonical
Corn
Canonical
Katana
Native
BTC.b
BTC.b is available on:
Ethereum
Native
Avalanche
Native (original chain)
Solana
Native
BTC.b uses the same Security Consortium and Chainlink infrastructure as LBTC.
How Bridging Works
Both LBTC and BTC.b use burn-and-mint bridging secured by multiple layers:
Burn — Tokens are burned on the source chain.
Verify — Chainlink CCIP validates the burn transaction.
Attest — Lombard's Token Developer Attestation confirms legitimacy.
Monitor — Symbiotic network independently verifies the transfer.
Mint — Tokens are minted on the destination chain.
This dual-layer verification ensures unauthorized minting is not possible.
Bridge LBTC
Using Lombard App
Go to lombard.finance/app
Connect your wallet on the source chain
Select Bridge
Choose the destination chain
Enter the amount of LBTC to bridge
Confirm the transaction
Wait for confirmation (typically 2–15 minutes)
LBTC arrives on the destination chain
Bridge Times
Ethereum ↔ Base
2–5 minutes
Ethereum ↔ Arbitrum
2–5 minutes
Ethereum ↔ BNB Chain
5–10 minutes
Ethereum ↔ Sui
5–15 minutes
Ethereum ↔ Solana
5–15 minutes
Times vary based on network congestion.
Bridge BTC.b
Using Lombard App
Go to lombard.finance/app.
Connect your wallet.
Select Bridge and choose BTC.b.
Select source and destination chains.
Enter amount and confirm.
Avalanche Users
BTC.b originated on Avalanche and has deep liquidity there. You can bridge BTC.b:
Avalanche → Ethereum: Through Lombard's bridge.
Avalanche → Solana: Through Lombard's bridge.
Within Avalanche ecosystem: Native transfers.
Bridging to Non-EVM Chains
Sui
LBTC can be bridged from Ethereum to Sui, and vice versa. After bridging via the Sui bridge, accessible from our dApp, users will receive wLBTC on their Sui address. This wLBTC on Sui must be claimed for LBTC on Sui. In order to this, users will need to ensure they have native SUI to cover the gas costs, and then, 1) From the Sui bridge page, after the bridge has been successful, LBTC can be converted to wLBTC by pressing convert.
Note: if you already closed this page, you can re-access this by entering the URL https://bridge.sui.io/transaction/{your_transaction_id}?chain=ETH.
where your_transaction_id is the transaction id from the origin chain, Ethereum. This can be found by using a block explorer like Etherscan or by checking your wallet's history.
2) After selecting claim, you will be prompted to approve a transaction in your Sui wallet. Note: this will cost some amount of SUI. 3) After approving, your wLBTC will be converted to LBTC on your Sui address.
Solana
Solana bridging uses LayerZero:
Connect an EVM wallet and a Solana wallet.
Select Solana as the destination.
Confirm the bridge transaction.
LBTC or BTC.b arrives as an SPL token.
Bridge Fees
Bridge fees depend on the route and cover:
Gas on source and destination chains.
CCIP messaging costs.
Fees are displayed before you confirm. Lombard does not charge additional bridge fees beyond network costs.
Bridge Security
Chainlink CCIP
Cross-Chain Interoperability Protocol provides the transport layer. CCIP validators must approve every transfer before minting occurs.
Symbiotic Guarantee Layer
Staked $BARD and LINK tokens back a monitoring network that verifies every bridge transaction. If a mismatch is detected between burn and mint events, staked collateral becomes slash-eligible.
BARD vault: 20M BARD cap.
LINK vault: $100M cap.
Security Consortium
Every bridge transaction requires approval from both CCIP validators and Lombard's Security Consortium—15 institutional members including OKX, Galaxy, Kraken, DCG, Wintermute, Figment, Kiln, and others.
LBTC vs BTC.b: Which to Bridge?
Earn yield while bridged
Yes
No
Lower fees
Similar
Similar
Chain availability
15+ chains
3 chains
Best for
Long-term DeFi use
Trading, flexibility
If you want yield, bridge LBTC. If you need BTC.b specifically for a protocol or chain where only BTC.b is supported, bridge BTC.b.
Converting Between Assets
You cannot directly bridge LBTC to BTC.b or vice versa. To convert:
LBTC → BTC.b:
Unstake LBTC to receive native BTC (9 days).
Mint BTC.b with your BTC.
BTC.b → LBTC:
Redeem BTC.b for native BTC.
Stake BTC to mint LBTC.
Alternatively, swap on DEXs where both assets have liquidity (may have slippage).
Frequently Asked Questions
Can I bridge directly between non-Ethereum chains?
Most routes go through Ethereum as a hub. Check the app for available direct routes.
What if my bridge transaction fails?
Funds remain on the source chain. If tokens were burned but not minted, contact support—the Security Consortium can resolve stuck transactions.
Is bridged LBTC the same as minted LBTC?
Yes. All LBTC is fungible regardless of chain. You earn the same yield and can use it in any DeFi protocol.
Can I unstake to BTC from any chain?
Yes. Initiate an unstake from any chain where you hold LBTC. BTC is delivered to your Bitcoin address after 9 days.
Does BTC.b earn Lux points?
BTC.b itself does not earn Lux. Only LBTC holdings and DeFi activities earn Lux.
Next Steps
Use LBTC — Stake BTC and mint LBTC
Use BTC.b — Mint and use BTC.b
Access DeFi — Deploy assets on destination chains
Troubleshooting — Get help with bridge issues
Last updated