Skip to Content
UseBridging

Bridging

Move your Bitcoin assets across blockchains. LBTC and BTC.b mint directly from native BTC on every supported chain, so bridging is only needed to move tokens you already hold from one chain to another. Lombard uses Chainlink CCIP for secure cross-chain transfers, with an additional economic guarantee layer powered by Symbiotic. Since September 2026, transfers between two non-Ethereum chains route through Ethereum.

Chain Support Update, September 2026

Native minting and redemption of LBTC and BTC.b are deprecated on TAC, Sonic, Katana, Berachain and Starknet, effective September 16, 2026. Holders on TAC, Sonic, Katana and Berachain must bridge all balances to Ethereum by December 10, 2026. The bridge between Ethereum and Starknet remains in place. Every other supported chain continues as today, including minting directly from BTC.

Full details, the deprecated chains table and the step-by-step migration guide are on the Chain Support Update page.

Lombard Assets

Lombard operates two Bitcoin assets, each available on multiple chains:

AssetTypeYieldPrimary Use
LBTCYield-bearing BTCYes (covered-call strategy)DeFi, long-term holding
BTC.bBridged BTCNoDeFi, trading, flexibility

Both assets are fully backed by native bitcoin and secured by the same Security Consortium.

Supported Chains

LBTC

LBTC mints natively from BTC on every chain below. To move LBTC you already hold between chains, each chain has a Chainlink CCIP burn-and-mint lane to Ethereum, listed in the Chainlink CCIP token directory  and co-signed by the Security Consortium.

Ethereum hub and Chainlink CCIP lanes (dual-layer security):

CCIP Chains
EthereumHub
AvalancheCCIP
BaseCCIP
BNB ChainCCIP
EtherlinkCCIP
MegaETHCCIP
MonadCCIP
SolanaCCIP
StableCCIP

Sui Bridge (non-EVM):

Sui Bridge
SuiNative

Starknet (bridge only):

Starknet
StarknetLock and Mint

Native minting and redemption on Starknet are deprecated, but the lock and mint bridge between Ethereum and Starknet remains in place. To redeem LBTC held on Starknet for BTC, bridge it to Ethereum first.

Deprecated (bridge to Ethereum only, until December 10, 2026):

Deprecated Chains
TACDeprecated
SonicDeprecated
KatanaDeprecated
BerachainDeprecated

Third-party canonical or lock-and-mint wrappers of LBTC on other networks are not issued by Lombard and are not covered by the Security Consortium.

BTC.b

BTC.b mints natively from BTC on every chain below. Transfers between them route through Ethereum:

ChainStatus
EthereumNative (hub)
AvalancheCCIP spoke (original chain)
MegaETHCCIP spoke
MonadCCIP spoke
StableCCIP spoke
KatanaDeprecated, bridge to Ethereum only until December 10, 2026

BTC.b uses the same Security Consortium and Chainlink infrastructure as LBTC. Live BTC.b supply per chain is published on the BTC.b transparency page .

How Bridging Works

Both LBTC and BTC.b use burn-and-mint bridging secured by multiple layers:

Burn
Tokens burned on source chain
Verify
CCIP validates the burn
Attest
Developer attestation confirms
Monitor
Symbiotic verifies independently
Mint
Tokens minted on destination

This dual-layer verification ensures unauthorized minting is not possible.

Routing Through Ethereum

Ethereum is the bridge hub. Every supported chain connects to Ethereum, and transfers between two non-Ethereum chains route through Ethereum rather than bridging directly. The app shows the routes available from your current chain.

Minting is unaffected. If you want LBTC on a specific chain, deposit BTC and choose that chain as the destination: no bridge is needed.

Bridge LBTC

Using Lombard App

  1. Go to lombard.finance/app .
  2. Connect your wallet on the source chain.
  3. Select Bridge.
  4. Choose the destination chain.
  5. Enter the amount of LBTC to bridge.
  6. Confirm the transaction.
  7. Wait for confirmation (typically 2-15 minutes).
  8. LBTC arrives on the destination chain.

Bridge Times

Ethereum - Base
2-5 min
Ethereum - Avalanche
2-5 min
Ethereum - BNB Chain
5-10 min
Ethereum - Sui
5-15 min
Ethereum - Solana
5-15 min
Ethereum - Monad
5-10 min

Times vary based on network congestion.

Bridge BTC.b

Using Lombard App

  1. Go to lombard.finance/app .
  2. Connect your wallet.
  3. Select Bridge and choose BTC.b.
  4. Select source and destination chains.
  5. Enter amount and confirm.

Avalanche Users

BTC.b originated on Avalanche and has deep liquidity there. You can bridge BTC.b:

  • Avalanche to Ethereum: Through Lombard bridge.
  • Avalanche to any other supported chain: Through Lombard bridge, routed via Ethereum.
  • Within Avalanche ecosystem: Native transfers.

BTC.b held on Katana must be bridged to Ethereum before December 10, 2026. It cannot be bridged from Katana back to Avalanche.

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 the dApp, you receive wLBTC on your Sui address. This wLBTC on Sui must be claimed for LBTC on Sui. Ensure you have native SUI to cover the gas costs, then:

  1. From the Sui bridge page, after the bridge completes, press Convert to convert wLBTC to LBTC.

If you already closed this page, re-access it by entering the URL https://bridge.sui.io/transaction/{your_transaction_id}?chain=ETH, where your_transaction_id is the transaction ID from Ethereum. Find this using a block explorer like Etherscan or by checking your wallet history.

  1. After selecting Claim, approve the transaction in your Sui wallet. This costs some amount of SUI.
  2. After approving, your wLBTC converts to LBTC on your Sui address.

Solana

Solana bridging uses Chainlink CCIP and is available for LBTC only. BTC.b is not deployed on Solana.

  1. Connect an EVM wallet and a Solana wallet.
  2. Select Solana as the destination.
  3. Confirm the bridge transaction.
  4. LBTC 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

Cross-Chain Interoperability Protocol provides the transport layer. CCIP validators must approve every transfer before minting occurs.

Symbiotic Guarantee Layer

Staked LINK backs a monitoring network that verifies LBTC and BTC.b cross-chain transfers. If a mismatch is detected between burn and mint events, staked collateral becomes slash-eligible. The LINK vault is capped at 100M USD.

Staked BARD also backed this layer, through a vault capped at 20M BARD, until the BARD staking program closed on September 17, 2026. See Staking BARD.

Security Consortium

Every bridge transaction requires approval from both CCIP validators and Lombard Security Consortium: 14 institutional members including OKX, Galaxy, Kraken, DCG, Wintermute, Figment, Kiln, and others.

LBTC vs BTC.b: Which to Bridge?

LBTC
Earn yield while bridgedYes
FeesSimilar
Chain availability10 chains
Best for: Long-term DeFi use
BTC.b
Earn yield while bridgedNo
FeesSimilar
Chain availability5 chains
Best for: 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 to BTC.b:

  1. Redeem LBTC to receive native BTC (up to 10 days).
  2. Mint BTC.b with your BTC.

BTC.b to LBTC:

  1. Redeem BTC.b for native BTC.
  2. Deposit BTC to mint LBTC.

Alternatively, swap on DEXs where both assets have liquidity (may have slippage).

Bridging FAQ

Can I bridge directly between non-Ethereum chains? No. Lombard uses a hub and spoke model anchored on Ethereum, so transfers between two spoke chains route through Ethereum. Check the app for the routes available from your chain.

I hold LBTC or BTC.b on TAC, Sonic, Katana or Berachain. What do I do? Bridge your full balance to Ethereum before December 10, 2026. Native minting and redemption on these chains are deprecated, and Ethereum is the only bridge destination. See Migrate from a Deprecated Chain.

I hold LBTC on Starknet. Do I need to do anything? No. The bridge between Ethereum and Starknet remains in place, with no deadline. Native minting and redemption on Starknet are deprecated, so to redeem for BTC, bridge to Ethereum first and redeem from there.

Can I still mint directly from BTC on other chains? Yes. Deposit native BTC and choose any supported chain as the destination. Native minting and redemption continue as before everywhere except the five deprecated chains.

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 redeem BTC from any chain? You can initiate a redemption from any supported chain where you hold LBTC. Redemption is deprecated on TAC, Sonic, Katana, Berachain and Starknet, so bridge to Ethereum first. BTC is delivered to your Bitcoin address in up to 10 days.

Does BTC.b earn Lux points? Starting in Season 3 (March 18, 2026), BTC.b earns Lux when deployed into eligible DeFi protocols.

LBTC also earns Lux exclusively through DeFi deployment.

Passive holding of either asset in a wallet does not generate Lux.

Visit the DeFi marketplace at lombard.finance/app  for eligible protocols, chains, and current multipliers.

Next Steps

Last updated on
Use BARDAccess DeFi