Sender Address

Overview

In an account-based blockchain, the sender address identifies the account whose authority is used to submit the transaction. The network checks its Transaction Nonce, available balance, signature, and any account-specific rules before execution. The sender may pay fees and initiate a transfer or contract call, although a sponsored-transaction design can separate the logical sender from the fee payer.

The concept is less precise in UTXO systems. A Bitcoin transaction consumes previous outputs, potentially controlled by several scripts or keys, and the protocol does not assign one universal “from address.” Wallets and explorers may infer source addresses from spent outputs, but that presentation can hide multiple owners, change behavior, or script conditions. Applications should not force account-model assumptions onto UTXO data.

The sender address also differs from the Transaction Sender when smart accounts, relayers, or contract-mediated execution are involved. A top-level transaction can be submitted by one account while an internal operation represents another user. Signature recovery, account-abstraction validation, and execution logs may each expose a different actor. Business logic must specify which identity it uses.

Payment systems should store the protocol-level sender data and avoid using it as the only proof of customer identity. Addresses can be newly generated, shared, compromised, or controlled by contracts. Screening and attribution should be network-aware and evidence-based. For outgoing payments, the final signing display should clearly show the source account, fee payer, network, and Recipient Address before authorization.

For dependable operation, store the network, top-level account or inputs, recovered authorization, fee payer, and any smart-account or relayer roles. This information is valuable because an explorer’s displayed “from” field may simplify several owners or execution actors into one address. Monitoring and response procedures should preserve protocol-native attribution and avoid treating the address alone as verified customer identity.