Native BTC and wrapped Bitcoin expose different transaction structures: Bitcoin UTXOs on one side and token contracts, approvals, and account history on the other.
Native BTC records
Bitcoin transactions consume UTXOs and create outputs. Fees and change are part of the same transaction graph.
Wrapped-token records
A wrapped representation on an EVM chain can involve ERC-20 transfers, approvals, contracts, and an account that accumulates other application activity.
The conversion path matters
Minting, custody, bridge, or swap infrastructure can explicitly connect representations or create provider records. Wrapped is not a privacy synonym.
Choose by asset and network needs
Verify the exact contract and route. Do not send WBTC to a native Bitcoin address or assume a BTC ticker means the same settlement system.
How to read the evidence
A representation comparison starts with contract or native-asset identity. Determine who or what creates and redeems the wrapped form, which chain records approvals or minting, and whether bridge or custody infrastructure adds another observable relationship. Similar economic value does not mean identical transaction history, security model, or receiving requirements. Always follow the specific representation named by the route.