How BTC Leaves Mainnet and Starts Working
Bitcoin on mainnet is pristine. It is also, for most users, idle.
The moment BTC leaves L1, it stops being just something you hold. It starts doing work. It becomes collateral in DeFi, moves into yield strategies, or turns into the asset you need if you want access to Stacks, Rootstock, ICP, or Merlin.
That is what this market really is: not a catalog of wrappers for its own sake, but a set of routes for turning BTC into something usable.
One clarification up front. Native BTC exists only on Bitcoin. Everywhere else, users are holding some BTC-backed representation with its own minting flow, trust model, and redemption rules. That distinction matters. But for most people, the first question is simpler:
Where should I move my BTC, and what do I actually get there?
If the goal is liquidity
This is still the easiest part of the market to read.
Some BTC assets win because they are the fastest route into the deepest parts of DeFi. That is the whole point.
WBTC is still the obvious starting point. It became the default DeFi version of BTC because integrations came first and liquidity followed. The tradeoff is not subtle: this is a custodial structure. But if the job is getting bitcoin into lending markets, DEX pools, and collateral venues with the least friction, that tradeoff is exactly what a lot of users accept. The WBTC is still the clearest place to start.
cbBTC is the cleaner exchange-native version of the same logic. Coinbase’s own wrapped BTC help page spells the route out directly: users can withdraw BTC to supported networks and receive cbBTC there. Its Exchange docs make the same point and currently list Base, Ethereum, Solana, and Arbitrum as supported routes. They also note that cbBTC is unavailable in some jurisdictions, including Canada, Georgia, and Japan.
That is why cbBTC matters. Not because it is philosophically elegant, but because if a user is already on Coinbase, it is one of the shortest ways to land in onchain BTC liquidity.
FBTC sits nearby, though the angle is slightly different. Function is pushing it as an omnichain BTC asset rather than something designed for one venue. If a user expects their BTC to move across ecosystems rather than stay parked in one pool, the FBTC docs are worth reading.
So this part of the market is pretty straightforward. If the goal is broad DeFi use, users usually go where liquidity is already thickest.
If the goal is yield
This is where the market gets more interesting.
A growing number of users are no longer looking for BTC that is merely usable. They want BTC that stays liquid while also earning.
LBTC is one of the cleaner direct routes into that trade. Lombard’s live LBTC FAQ lays the flow out simply: send BTC to the generated deposit address, wait for six Bitcoin confirmations, and LBTC mints to the destination wallet. That same page currently says LBTC is available on 15+ chains, explains that LBTC is yield-bearing, and notes that unstaking takes 9 days. For users trying to understand how the asset moves after minting, Lombard’s Bridging and Transparency sections are the useful follow-ups.
That directness is a big part of LBTC’s appeal. You start with native BTC. You do not need another wrapper first.
SolvBTC follows a similar logic, though it belongs to a broader BTC finance stack. Solv’s overview describes SolvBTC as an on-chain Bitcoin reserve asset, fully backed by Bitcoin under defined rules for minting, custody, and redemption. Its current Minting & Redemption docs are worth checking closely because they make one operational point very clear: redemptions happen on a set schedule, and the schedule depends on the specific product. That is exactly the kind of detail users notice too late if nobody says it plainly.
eBTC from ether.fi is a different kind of yield route. It is not really the cleanest first step from native BTC. It is what users reach for once they already hold wrapped BTC and want more out of it. The eBTC docs describe it directly: eBTC is backed by LBTC, users can deposit LBTC and WBTC, and the appeal is dual yield through staking plus restaking, with multiple points programs layered on top.
That is the real dividing line here. LBTC and SolvBTC are cleaner starting points for users coming from native BTC. eBTC makes more sense once someone is already deeper inside the wrapped BTC stack.
If the trust model matters more than convenience
Some users are perfectly fine with exchange-backed or custodian-backed BTC if the liquidity is there. Others are not.
That is where the more bitcoin-aligned routes start to matter.
Threshold’s live tBTC Minting Walkthrough explains the setup without much fluff: users need BTC, a Bitcoin wallet, an Ethereum wallet, and ETH for gas. That already tells you what kind of route this is. Not the simplest one in the market, but one built for users who want BTC in programmable environments without taking the most obvious custodial shortcut.
sBTC makes more sense if you think about destination first and wrapper type second. This is BTC for Stacks. Stacks’ current docs on Dual Stacking note that the minimum to mint sBTC through the bridge app is `0.001 BTC`. If the user wants access to the Stacks ecosystem, that is the route that matters.
ckBTC on the Internet Computer solves a different problem. It is less about becoming the biggest BTC asset in DeFi and more about making BTC cheap and fast to use inside ICP. The ckBTC overview currently lists a transfer fee of `0.0000001 ckBTC` and describes the asset as backed 1:1 by BTC. The ICP Bitcoin dashboard is useful if a reader wants the broader chain-key Bitcoin context after that.
rBTC on Rootstock is one of the older BTC-to-smart-contract routes still standing. Rootstock’s own PowPeg guide currently states a `0.005 BTC` minimum and explicitly warns that sending less than that can lead to loss of funds. That is exactly the sort of sentence users should see before they bridge, not after.
This whole part of the market is smaller than the liquidity-first segment, but the motivation is usually stronger. People choosing these routes tend to know why they are choosing them.
If what you really want is one ecosystem
Some BTC assets do not need to be judged against the whole market. They only need to be judged against the ecosystem they are meant to enter.
Merlin BTC belongs in that category. Merlin Chain is a Bitcoin L2, and its own docs frame the bridge as a route for moving BTC from Bitcoin L1 into the Merlin environment. The practical part matters more than the branding: Merlin’s Official Bridge currently supports bidirectional bridging between Bitcoin Layer1 and Merlin Chain, and the docs currently show estimated bridge costs of 0.003 BTC from BTC to Merlin and 0.00002 BTC in the reverse direction. Merlin M-Token docs explain the logic behind M-BTC as the Layer2 representation of staked BTC inside the Merlin ecosystem.
That makes Merlin BTC easy to place on the map. You do not go there because it is the most universal BTC wrapper. You go there because you want Merlin itself.
UBTC on Hyperliquid is a different case, but the same kind of decision. Hyperliquid’s own docs show that users can deposit BTC on the Bitcoin network directly into Hyperliquid, and its onboarding guide lists BTC on Bitcoin as a supported deposit route. The more operational details sit in Hyperliquid’s Bitcoin deposit support page: Bitcoin deposits are managed by Unit Protocol, the minimum deposit is 0.0003 BTC, and deposits typically take around 30 minutes to arrive. Hyperliquid’s API docs also note that what appears as BTC/USDC in the app corresponds to UBTC/USDC on mainnet HyperCore.
So the user choice here is not abstract. If the destination is Merlin, use the Merlin route. If the destination is Hyperliquid spot and HyperCore liquidity, UBTC is the relevant rail.
So where does ordinary BTC actually go?
For pure DeFi liquidity, WBTC and cbBTC are still the obvious starting points. For yield, LBTC and SolvBTC are cleaner routes from native BTC, while eBTC is better suited to users who already hold wrapped BTC.
And if the goal is access to one specific ecosystem, the answer is usually simple: use the BTC asset built for that ecosystem instead of forcing a general-purpose wrapper where it does not really belong.
The branding makes this market look crowded. For users, the choice is usually much narrower than that.
In practice, most users are deciding just four things: where BTC is easiest to use, where it can earn, how much trust they are willing to outsource, and which ecosystem they actually want to enter.
Try:
₿itcoin ecosystem dashboard overview
Our Infrastructure Builders Program
Follow us for more updates and support:
- X(Twitter): @htwtech_
- Telegram: @htwtech
- Medium: High Tower
