Bitcoin and Ethereum are often described with the same verbs: send, receive, hold. The records underneath those verbs are different. Bitcoin tracks outputs that are created and then consumed. Ethereum tracks accounts that persist and whose balances are updated. Mixing the two pictures produces bad explanations of fees, of “change,” and of what a contract can remember.
Two kinds of Ethereum account
Ethereum.org describes two account types. An externally owned account is controlled by a private key. A contract account is controlled by its code. Both have a state that includes a nonce and a balance. A contract account also has code and storage. An externally owned account has no code. The address of an externally owned account is derived from the public key. The address of a contract is derived from the creator’s address and nonce, or from a creation formula when a contract creates another contract.
The nonce is a counter, not a secret. For an externally owned account it counts transactions sent. For a contract it counts creations. Repeating a transaction does not create a second spend of the same coins in the Bitcoin sense. The protocol rejects a transaction whose nonce is not the next one it expects. That is how Ethereum orders an account’s transactions and avoids a simple replay.
A balance is a field
An Ethereum balance is a number in the account state, denominated in wei. A transfer subtracts from one account and adds to another, if the sender has enough and the transaction is valid. There is no requirement to consume the entire balance and send change to yourself. If you hold 2 ETH and you transfer 0.4 ETH, the protocol’s picture is a smaller balance, not a new coin that replaces an old coin.
That sounds closer to a bank ledger than Bitcoin does. It still is not a bank. The balance is not a promise from an intermediary. It is a field that every validating node recomputes by executing transactions. A wallet that shows a different number is either looking at a different state, counting tokens that are not ETH, or using an account you do not fully control.
What contracts can remember
Contract storage is the important extra. A token contract can keep a mapping from addresses to balances. Those token balances are not ETH balances. They are numbers in that contract’s storage. Destroying the ETH in an account, or sending ETH to the wrong place, does not automatically move the tokens. The token contract has its own rules for who may rewrite its mapping.
Bitcoin can also express conditions that are more interesting than “this key may spend,” and it can carry data. It does not give each coin a persistent account that accumulates storage across calls. If you are reading an Ethereum transaction, look for the account nonce, the value in wei, and whether the target is a contract that will run code. If you are reading a Bitcoin transaction, look for inputs that consume outputs and for new outputs, including change. The words “wallet balance” hide that fork.
The same payment, told both ways
Suppose you are paying someone the equivalent of a small invoice. On Bitcoin the wallet selects one or more UTXOs whose sum covers the invoice and the fee. It writes an output for the recipient and, if anything remains, a change output back to you. The old outputs are gone after confirmation. On Ethereum the wallet builds a transaction from your account with a nonce, a value in wei, and a gas limit. The recipient’s balance field increases and yours decreases if the transaction is included and the account holds enough. There is no change output. There is a fee, paid in ETH, which is gas rather than a leftover of the invoice.
The failure modes differ in the same way. A stuck Bitcoin payment is an unconfirmed transaction that has not yet consumed its inputs, and those inputs cannot safely be spent a second time until the conflict is resolved. A stuck Ethereum payment is often a transaction with a nonce the network has not accepted yet, which holds up every higher nonce from that account. Replacing it means sending the same nonce again with a higher fee, not building a change output. Wallets that use one vocabulary for both chains will describe both situations as “pending.” The records underneath are not pending in the same sense.
Sources
- Ethereum.org, Ethereum accounts.
- Ethereum.org, Transactions.
- Bitcoin white paper, on transaction outputs.




