RenBridge is a reference hub for comparing wrapped Bitcoin, sidechain BTC and BTCFi assets before you move value off Bitcoin L1. Review WBTC, cbBTC, tBTC, BTC.b, RBTC, L-BTC and staking-linked BTC variants across Ethereum, Base, Solana, Arbitrum, Avalanche, Stacks, Rootstock and Liquid, while the old RenVM renBTC route is sunset.
The widget is illustrative only; there is no wallet connection here.
BTC
WBTCThe widget is illustrative only; there is no wallet connection here.
Most BTC bridge flows start with native BTC or an existing wrapped BTC position, then route through the issuer, bridge or protocol that supports the destination chain. The important question is who controls redemption back to Bitcoin.
Bridge-style systems usually lock or custody BTC before minting a representation on another chain, then burn or redeem that representation before releasing BTC back. The tBTC documentation describes a threshold-network model for this kind of Bitcoin bridge flow.
Wrapped Bitcoin routes differ by control model: a custodian for WBTC or cbBTC, a federation for Liquid and Rootstock-style pegs, TSS/MPC for FBTC-style custody, DLC escrow for dlcBTC/iBTC, collateralized vaults for interBTC and signer-set pegs for sBTC. Interlay is the factpack example of a collateralized vault design.
Timing depends on Bitcoin confirmations, destination-chain settlement and the issuer or protocol's redemption workflow. Avoid assuming a fixed settlement window: BTC.b documentation, for example, frames bridge movement around confirmation and redemption mechanics rather than a universal clock. See BTC.b technical specifications.
Custodian-backed wrapped Bitcoin with the deepest DeFi support. A named issuer holds the BTC and mints the token; access and redemption follow that issuer's rails.
BitGo · Custodial
WBTC wraps BTC through BitGo-linked custodians and merchants for Ethereum, Arbitrum, Base, Optimism and Polygon.
Bridge BTC
Coinbase · Custodial
Coinbase holds native BTC and issues cbBTC for Base, Ethereum, Solana and Arbitrum access.
Bridge BTC
Binance · Custodial
BTCB is Binance-Peg Bitcoin for BNB Chain, with Binance custody behind the BTC reserve.
Bridge BTC
Lombard · Consortium
BTC.b is Lombard-operated bridged Bitcoin rooted in Avalanche infrastructure. Native BTC backing sits under a consortium, proof, timelock and approval design. It now extends to Ethereum and Katana, so users should confirm the exact network and redemption route before moving funds, including supported contracts, issuer approvals and destination-chain liquidity first.
Bridge BTC
Function · MPC/TSS
FBTC uses Function's MPC/TSS custody design to represent BTC across Ethereum, BNB Smart Chain, Arbitrum, Base, Mantle and Sonic.
Bridge BTC
21.co · Custodial
21.co issues 21BTC against BTC reserves, with Chainlink Proof of Reserve used for transparency. It is available on Solana and Ethereum, so the issuer and contract matter as much as the chain.
Bridge BTC
Kraken · Custodial
Kraken custodies one native BTC for each kBTC and supports wrapped Bitcoin use on Ethereum and Optimism.
Bridge BTCBridges that replace a single custodian with threshold signatures, DLC escrow or collateralized vaults. Trust shifts to a protocol and its operators, not one company.
Threshold · Threshold sig Decentralized
tBTC bridges BTC through Threshold Network operator groups using threshold cryptography. It reaches Ethereum, Arbitrum, Base, Optimism and Polygon, reducing reliance on a single BTC custodian but still requiring bridge and contract checks.
Bridge BTC
DLC.Link · DLC escrow Decentralized
dlcBTC locks BTC in DLC-based Bitcoin escrow, with attestors enabling minting on Arbitrum and Ethereum. It is active but has narrower liquidity and integrations than larger custodial wrappers, so route availability needs checking. Use it when that DLC custody model fits the job and the supported chain is clear before signing.
Bridge BTC
DLC.Link · DLC multisig Decentralized
iBTC Network represents BTC through 2-of-2 Bitcoin multisig and DLC-based mint and burn flows. It spans iBTC Network and Ethereum, but users should verify current chain support before moving funds.
Bridge BTC
Interlay · Vault collateral Decentralized
interBTC uses Interlay's collateralized vault model: BTC is locked by permissionless vaults that post collateral and support redemption. It can touch Polkadot, Kusama, Ethereum and Moonbeam, but the route is harder because ticker overlap, vault conditions and chain support require care. Check the exact asset before you bridge BTC there.
Bridge BTC
pNetwork · Uncertain Verify status
pBTC relied on pNetwork bridge vaults and validator-controlled mint/burn processes across Ethereum, BNB Smart Chain and EOS. Its current status is uncertain, so verify redemption paths directly before treating it as usable.
Verify statusSidechain and layer assets where BTC is pegged into a separate chain rather than wrapped as an ERC-20. The peg, not a custodian contract, defines how you exit back to L1.
Stacks · Signer peg L2
Stacks sBTC uses a signer-managed Bitcoin peg wallet and mints on Stacks after Bitcoin confirmation.
Bridge BTC
Rootstock · PowPeg Sidechain
RBTC is Rootstock's sidechain BTC asset, backed through the PowPeg rather than an ERC-20 wrapped Bitcoin issuer. Peg operations depend on Rootstock bridge consensus and PowHSM controls, so it belongs in the sidechain category.
Bridge BTCLiquid · Federation Sidechain
L-BTC is Liquid Network's federated sidechain Bitcoin representation. The Liquid Federation manages the peg, and public users may need federation members or supported services for peg-out. It is active, but redemption access differs from a normal exchange withdrawal and should be checked before routing, including member access and wallet compatibility.
Bridge BTCBitcoin routed through Babylon-linked staking and issued as a liquid token. These are protocol products with staking and redemption mechanics layered on top of the BTC representation — not plain wrapped BTC.
Lombard · Babylon LST LST
Lombard LBTC represents BTC staked through Babylon and issued as liquid staked Bitcoin. It spans Ethereum, Base, BNB Smart Chain, Sui and Solana, adding BTCFi mechanics to the custody and redemption picture.
Bridge BTC
Solv · Reserve asset LST
SolvBTC is Solv Protocol's onchain Bitcoin reserve asset across Ethereum, BNB Smart Chain, Arbitrum, Base and Merlin.
Bridge BTC
Solv · BTCFi LST LST
xSolvBTC is a yield-bearing Solv BTC variant tied to Babylon ecosystem staking and Solv reserve architecture. It can appear on Ethereum, BNB Smart Chain, Arbitrum and Base, but it is not the same risk profile as plain wrapped Bitcoin. Treat the staking layer as part of the route decision too.
Bridge BTC
PumpBTC · Babylon LST LST
pumpBTC routes wrapped BTC assets through PumpBTC partners and Babylon staking to issue liquid tokens. It is active on Ethereum, BNB Smart Chain and Mantle, with protocol and custody-partner execution risk.
Bridge BTC
Bedrock · Restaking LST LST
Bedrock uniBTC starts from supported wrapped BTC deposits, then adds staking or restaking exposure managed by Bedrock.
Bridge BTC
Lorenzo · Staking agent LST
Lorenzo stBTC is a Babylon staking principal token issued after qualified staking agents receive BTC and provide proof. It appears on Lorenzo Chain, Ethereum and BNB Smart Chain, and settlement depends on the staking-agent process.
Bridge BTC
Merlin · Uncertain Verify status
M-BTC is a Merlin Chain mapped BTC representation or asset voucher from Merlin staking and bridge flows. Its current bridge and redemption status is uncertain, so verify official support before using it.
Verify statusIncluded because people search “Aave BTC”: aWBTC is the receipt you get for supplying WBTC to Aave. It is a claim on pool-supplied WBTC, not a way to bridge native Bitcoin.
Aave · Lending receipt Not a bridge
aWBTC is Aave's lending receipt for supplied WBTC on markets such as Ethereum, Polygon, Arbitrum, Optimism and Base. It is not a BTC bridge, not a native BTC asset and not a wrapped-BTC issuer. Treat it as a claim on pool-supplied WBTC inside Aave markets rather than native Bitcoin exposure.
Open AaveSome BTC variants are harder to bridge because they depend on narrower liquidity, chain-specific wallets, protocol-managed staking, issuer redemption or current-status checks. Interlay is a useful example of how a BTC route can be active but still operationally different from a custodial wrapped token.
| BTC variant | Why it’s harder to bridge | How to route it |
|---|---|---|
| interBTC | It uses collateralized vaults and supports redemption through Interlay's model, so the route is more specialized than a simple exchange-issued wrapper. | Verify the supported chain, vault/redemption route and ticker context because iBTC can refer to other assets. |
| dlcBTC / iBTC | The DLC-based model is narrower than major custodial wrappers and depends on the relevant DLC.Link or iBTC Network flow. | Confirm whether your destination chain supports the exact asset and whether the route uses dlcBTC or the newer iBTC branding. |
| xSolvBTC | It is a yield-bearing SolvBTC variant tied to Solv's reserve architecture and Babylon ecosystem staking exposure. | Treat it as BTCFi, not plain wrapped BTC, and check redemption, supported chains and protocol terms before moving funds. |
| stBTC | Lorenzo's stBTC involves qualified staking agents, staking proof and principal-token accounting rather than a basic wrapped BTC mint. | Check Lorenzo Chain, Ethereum or BNB Smart Chain support and understand the staking-agent process before routing. |
| pumpBTC | pumpBTC routes wrapped BTC assets through partners and Babylon-focused liquid-staking mechanics. | Verify partner custody, supported networks and redemption mechanics directly from PumpBTC documentation. |
| uniBTC | Bedrock accepts supported wrapped BTC and adds staking or restaking exposure, so it carries protocol-layer mechanics beyond bridging. | Use Bedrock's supported asset list and chain support before assuming a direct native-BTC bridge path. |
| pBTC / M-BTC | Both have uncertain current bridge or redemption status in the factpack and should not be treated as standard active routes. | Verify the current pNetwork or Merlin documentation, supported chains and redemption availability before any use. |
Legacy BTC wrappers can remain visible in wallets, DEX pairs and search results after their practical bridge routes have changed. Use current issuer or protocol documentation, and treat the old Ren client docs as historical context for RenBridge and RenVM.
renBTC was the RenVM-era BTC asset, but Ren 1.0 was sunset after the Alameda/FTX collapse. Do not use RenBridge as a live BTC-to-renBTC bridge; start from the Ren client docs only for historical context.
HBTC is a legacy Huobi/HTX-era BTC wrapper on Ethereum with weak current reserve and redemption assurances in the factpack. Treat the Huobi BTC listing as an identity reference, not a route recommendation.
imBTC is a Tokenlon-issued ERC-777 BTC representation and should be framed as legacy, not as a current bridge path. The imBTC FAQ is useful for definition and history.
Bridge cost and risk come from components, not a single universal quote. Compare the fee stack, custody model and redemption path before choosing a wrapped Bitcoin route.
Expect a Bitcoin miner fee, a bridge or protocol fee where applicable, destination-chain gas and any redemption or withdrawal cost. Those components can change with network conditions and with the issuer or protocol route.
Who controls the underlying BTC differs by model: BitGo/WBTC-style custodians, Coinbase account-linked custody, Binance-pegged reserves, federated sidechains, threshold signing groups, DLC escrow, signer sets and collateralized vaults. The Wrapped Bitcoin site is the main factpack source for the custodial WBTC model.
Wrapped and bridged BTC can face peg-stability pressure, bridge or contract exposure, liquidity gaps and redemption limits. BTCFi liquid-staking tokens add protocol-managed staking and reward-accounting mechanics, so review sources such as Babylon liquid staking tokens before treating them like plain BTC wrappers.
Bridging is irreversible once settled; verify chain, contract and issuer before confirming.