Bitcoin UTXO and account-chain boundary
Bitcoin uses a UTXO source model while Solana uses a non-UTXO destination model. Native Bitcoin deposits require a supported Bitcoin address, confirmation-aware input handling, and attention to change outputs; an EVM token labeled BTC or WBTC is not native BTC.
Solana receipt-side execution
Solana is a L1 SVM network in the Solana ecosystem. SOL pays destination-side network gas on Solana. Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.
Bitcoin deposit-side execution
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays source-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth.
Choose an asset that exists on both route sides
The live quote lists the exact Bitcoin input asset and Solana output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Bitcoin to Solana bridge mistakes
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Solana; running out of BTC before the source transaction is submitted; assuming bitcoin and solana addresses are interchangeable. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.