Route family
Bitcoin routes that enter another ecosystem
Use this family when the route starts in BTC but the real goal is another native asset ecosystem such as Ethereum, Solana, or BNB Chain.
Total routes:1027
Featured now:22
Mapped next:1005
Curated seeds:3
What this route family covers
BTC-to-alt routes matter when Bitcoin is only the starting asset. The destination ecosystem is the real decision because wallet type, app environment, and native settlement all change after the route finishes.
These pages help compare where BTC is most often deployed next, especially when the destination chain needs native assets rather than another stable landing asset.
How to compare routes in this family
Choose the destination ecosystem first
The biggest question is usually where BTC should go next: Ethereum, Solana, BNB Chain, or another native environment with its own wallet and app context.
Then compare destination settlement type
Some routes end in native L1 assets, others in L2 or ecosystem-adjacent assets. That changes what the user can do immediately after settlement.
Keep BTC source variants secondary
For this family, the destination ecosystem usually matters more than whether the source starts as native BTC or another Bitcoin-linked variant.
Representative BTC ecosystem-entry routes
These examples prioritize the clearest ecosystem-entry paths that begin from BTC and end in native destination assets such as ETH, SOL, or BNB before expanding into more specialized variants.
BTC
ETH
Useful when the user wants to move from BTC into native ETH for on-chain activity in the destination ecosystem.
Bitcoin → Ethereum
BTC
SOL
Useful when the user wants to move from BTC into native SOL for on-chain activity in the destination ecosystem.
Bitcoin → Solana
BTC
BNB
Useful when the user wants to move from BTC into native BNB for on-chain activity in the destination ecosystem.
Bitcoin → BNB Chain
BTC
TON
Useful when the user wants to move from BTC into native TON for on-chain activity in the destination ecosystem.
Bitcoin → TON
BTC
XRP
Useful when the user wants to move from BTC into native XRP for on-chain activity in the destination ecosystem.
Bitcoin → Ripple
BTC
ETH
Useful when the user wants to move from BTC into native ETH for on-chain activity in the destination ecosystem.
Bitcoin → Base
BTC
ETH
Useful when the user wants to move from BTC into native ETH for on-chain activity in the destination ecosystem.
Bitcoin → Arbitrum
BTC
ARB
Useful when the user wants to move from BTC into native ARB for on-chain activity in the destination ecosystem.
Bitcoin → Arbitrum
BTC
cbBTC
Useful when the user wants to move from BTC into native cbBTC for on-chain activity in the destination ecosystem.
Bitcoin → Ethereum (ERC20)
Bitcoin source assets
These are the Bitcoin-native or Bitcoin-linked starting assets that most often fund ecosystem-entry routes.
Common BTC starting networks
Most high-intent routes begin from native Bitcoin, but the family also includes Bitcoin-linked assets on other chains where the source environment changes before ecosystem entry.
Common destination ecosystems
The destination network is usually the real decision in this family because it determines app compatibility, wallet type, and what can happen next after settlement.
BTC-to-alt family FAQ
What should I compare first in BTC-to-alt routes?
Start with the destination ecosystem. The most important difference is usually whether the route should end in Ethereum, Solana, BNB Chain, or another native chain environment.
Why is this family different from BTC-to-stable routes?
BTC-to-stable routes are mostly about reducing volatility, while BTC-to-alt routes are about deploying Bitcoin value into another ecosystem for on-chain activity, wallet compatibility, or app access.
Should native BTC routes be prioritized over Bitcoin-linked variants here?
Usually yes for representative examples. Native BTC gives the clearest ecosystem-entry route, while Bitcoin-linked variants are useful but more secondary inside the family map.
Why do destination networks matter more than source context in this family?
Because the route usually exists to reach a new ecosystem. Once the user decides to leave Bitcoin, the destination chain and asset determine the real utility of the route.
Related route families
These related families usually sit one decision away from the current cluster. Use them to compare whether the next route should preserve value, end in BTC, or enter another ecosystem instead.
Stablecoin to ecosystem-entry routes
Use this family when the funding asset stays stable at the start, but the destination should become a native ecosystem asset such as ETH, SOL, or BNB.
2072 total routes | 24 featured now | 2048 more in this family
Altcoin to BTC routes
Use this family when the route starts from a non-Bitcoin asset and the destination should settle as native Bitcoin.
69 total routes | 7 featured now | 62 more in this family
BTC to stable routes
Use this family when the route starts in BTC and ends in a stable destination so volatility can drop before the next transfer, treasury step, or portfolio move.
814 total routes | 13 featured now | 801 more in this family
Ready to open a route?
Move from this family view into the live builder or open one of the top routes above when the pair and network direction are already clear enough to act on.