Native Bitcoin and wrapped Bitcoin are not the same asset even when a market uses a BTC-like ticker. Native BTC is secured on the Bitcoin network; a wrapped or bridged token is issued on another network and depends on an issuer, custodian, bridge, or redemption design. Compare the exact identifiers before comparing balances.
Native BTC
Native bitcoin uses Bitcoin addresses, Bitcoin transaction rules, miners, and Bitcoin wallet software. The private key controls the native balance on that network. Fees, confirmations, address formats, and recovery procedures belong to Bitcoin.
Wrapped or bridged BTC
A representation on Solana or another chain has a token mint, token program, issuer or bridge mechanism, and its own transfer fees. Its value may track BTC, but tracking depends on reserves, redemption, market liquidity, and operational controls. A ticker is not proof of backing.
Custody and redemption questions
Ask who holds the native BTC, who can mint or freeze the representation, how redemption works, what proof is published, which network is supported, and what happens during a pause. Record source URLs and dates because bridge and issuer arrangements change.
Using it on Jupiter
Bitcoin on Solana and buying Bitcoin on Jupiter explain why a Solana swap can produce a tokenized representation rather than a native Bitcoin withdrawal. Check the output mint and destination network before signing.
Research output
Write “native BTC” or the exact token mint in every report. Do not add the assets together without stating the custody and redemption assumptions. Treat a bridge failure, freeze, or thin market as a different risk from Bitcoin confirmation delay.
Limits and responsible use
This guide does not identify or endorse a specific wrapped asset. Verify issuer, mint, reserves, and redemption rules from current primary sources before interacting. Last reviewed 2026-09-21.