Native Transfer

Overview

Native Transfer moves the asset defined by the base protocol. On Bitcoin, the transaction spends UTXOs and creates new outputs denominated in bitcoin. On Ethereum, a transaction can set a value amount for the destination account. No separate token contract is required to record the base-asset balance change.

Native assets commonly serve a second purpose as fee assets. A wallet sending a token may still need native currency for gas, while a native transfer pays its fee from the same asset family. The amount received and the fee charged are separate transaction effects and should be displayed clearly.

The transfer can still execute code. Sending ether to a contract may trigger its receive or fallback logic, and the call can fail. A transaction to an ordinary account is simpler, but the sender must still use the correct network, nonce, balance, and Gas Limit.

A native transfer differs from a Token Transfer, which updates balances maintained by a contract or program. Indexers often detect token movement from event logs, while native movement can be represented directly in transaction fields or internal execution traces.

Payment systems should verify the asset type explicitly. The same address format may receive both native currency and tokens, but an invoice expecting one should not credit the other. Confirmation tracking, exchange-rate locking, and reconciliation should bind the Blockchain Transfer to the intended native asset and network.

Networks also differ in how native movement inside contract execution is exposed. The top-level transaction value may show only the initial transfer, while nested calls move additional value. Support and accounting tools may need execution traces to identify these internal movements and avoid misreporting the recipient or total amount.