Ethereum Explained: ETH, Gas, Smart Contracts, Transactions and Wallet Safety

Use this glossary as a process map rather than a list to memorize. Start with ETH and the Ethereum network, follow what happens when a wallet signs a transaction, then use the relationship map to identify where gas, smart contracts, confirmations and transaction hashes fit. The “Do Not Confuse” section highlights mistakes that can cause failed transactions or permanent loss.

Essential Ethereum Glossary

Ethereum

Exact meaning: Ethereum is a programmable blockchain platform whose nodes maintain a shared state and execute transactions and smart-contract code. In plain English: it is the environment in which ETH moves and Ethereum applications operate. Where it appears: wallet network selectors, exchange deposit and withdrawal instructions, application documentation and block explorers. Decision affected: before sending an asset, confirm that both sender and recipient support the same Ethereum network rather than relying on the appearance of the address alone. Ethereum Mainnet is distinct from Ethereum-compatible networks and layer 2 systems. ^[1]

Blockchain

Exact meaning: a blockchain is the replicated record through which network participants agree on transactions and the resulting state. In plain English: it is the public record that shows which confirmed actions changed balances or contract data. Where it appears: technical documentation, wallet transaction histories and block explorers. Decision affected: use blockchain data to verify a submitted transaction instead of treating a wallet notification, email or screenshot as final proof.

ETH and ether

Exact meaning: ether is Ethereum’s native asset, represented by the ticker ETH. It is held directly by Ethereum accounts and is used to pay execution fees on Ethereum. In plain English: ETH is both a transferable coin and the asset used to pay for on-chain computation. Where it appears: account balances, transfer forms, gas estimates and explorer records. Decision affected: keep enough ETH on the network being used to pay for a planned state-changing transaction, including an ERC-20 token transfer or smart-contract interaction. ^[2]

Ethereum account

Exact meaning: Ethereum has externally owned accounts controlled through private keys and contract accounts controlled by deployed code. Both types can hold ETH and tokens, but only an externally owned account can initiate a transaction directly. In plain English: one account follows a user’s valid signature; the other follows a program. Where it appears: wallet documentation, explorer address pages and smart-contract interfaces. Decision affected: determine whether the destination is a user-controlled address or a contract, because sending a token to an incompatible contract can leave it inaccessible. ^[3]

Address

Exact meaning: an Ethereum address identifies an externally owned account or contract account. Standard hexadecimal Ethereum addresses begin with 0x. In plain English: it tells the network which account or contract a transaction targets; it does not prove that the selected network or recipient is correct. Where it appears: receiving screens, withdrawal forms, contract documentation and explorer searches. Decision affected: compare the full destination using a trusted source, verify the network separately and consider a small test transaction where appropriate. ^[3]

Private key

Exact meaning: a private key is secret cryptographic data used to authorize actions for an externally owned account by signing transactions or messages. In plain English: possession of the key means control of the account. Where it appears: secure wallet backup or export functions, although routine transfers should not require revealing it. Decision affected: never enter a private key into an exchange form, block explorer, support chat or unfamiliar website. Ethereum contract accounts do not have private keys of their own; their behavior is governed by code. ^[4]

Seed phrase or recovery phrase

Exact meaning: a seed phrase is a sequence of words from which a wallet can derive private keys and accounts. In plain English: it may restore an entire wallet rather than authorizing only one transfer. Where it appears: wallet creation and recovery procedures, not normal send or receive screens. Decision affected: keep it offline and private; anyone who obtains it may gain access to multiple derived accounts and assets. No legitimate recipient needs it to send you ETH. ^[4]

Transaction

Exact meaning: an Ethereum transaction is a cryptographically signed instruction from an externally owned account that requests a change to network state. It may transfer ETH, deploy a contract or call a function on an existing contract. In plain English: it is the signed action the network is asked to execute. Where it appears: wallet confirmation screens, pending-activity lists and explorer records. Decision affected: inspect the destination, network, value, requested contract action and maximum fee before signing; a familiar website design does not make a transaction safe. ^[5]

Smart contract

Exact meaning: a smart contract is code and persistent data deployed at an address on Ethereum. Users interact with it by submitting transactions that call its functions. In plain English: it is a program that runs under blockchain rules when invoked. Where it appears: token contracts, decentralized exchanges, lending applications, bridges and contract pages in explorers. Decision affected: verify the application and contract address before approving an interaction; code execution can transfer tokens, change permissions or perform several actions within one transaction. Contract interactions are generally irreversible once executed. ^[6]

Token

Exact meaning: a token on Ethereum is usually represented and accounted for by a smart contract. ERC-20 defines a common interface for fungible tokens, including balance, transfer and spending-approval functions. In plain English: unlike native ETH, an ERC-20 balance is managed by contract logic. Where it appears: wallet token lists, token contract pages, approvals and application interfaces. Decision affected: verify the token contract and network, not just its name or ticker; unrelated assets can use identical symbols. Sending tokens to a contract that cannot handle them may make the assets inaccessible. ^[7]

Gas

Exact meaning: gas is the unit used to measure the computational work required to execute operations on Ethereum. In plain English: gas measures work, not the market value of the transferred asset. A simple ETH transfer usually requires less computation than a multi-step smart-contract call. Where it appears: wallet estimates, transaction details, developer documentation and explorers. Decision affected: check whether the wallet is estimating gas for a plain transfer, token transfer or contract interaction; they are not interchangeable operations. ^[8]

Gas limit

Exact meaning: the transaction gas limit caps how many gas units the transaction may consume. Unused gas is not charged as if it had been consumed. In plain English: it is a work ceiling, not necessarily the final fee. Where it appears: advanced wallet settings and explorer transaction data. Decision affected: lowering it without understanding the operation can cause execution to run out of gas; a failed execution can still consume gas because the network performed computational work. ^[8]

Network fee

Exact meaning: the fee is the amount paid for the gas actually used, based on the applicable price per gas unit. On Ethereum Mainnet, its components include a protocol-defined base fee and a priority fee that incentivizes inclusion. Wallets may also display a maximum fee cap. In plain English: gas measures work, while the fee is the ETH cost of that work. Where it appears: wallet previews and explorer fee details. Decision affected: review the maximum possible charge before signing and do not confuse a network fee with an exchange’s conversion rate or service charge. Fees vary with the operation and network conditions. ^[8]

Transaction hash or txid

Exact meaning: a transaction hash is the cryptographic identifier generated for a submitted transaction. In plain English: it is the reference used to locate the transaction in an explorer. Where it appears: wallet histories, withdrawal records, deposit support requests and block explorers. Decision affected: search the txid on an explorer for the actual network used and compare status, sender, recipient, value and token-transfer records. A txid proves that a transaction record exists; it does not by itself prove that the intended recipient credited an off-chain account. ^[9]

Confirmation and finality

Exact meaning: inclusion means a validator placed the transaction in a block; later blocks and Ethereum’s consensus process increase confidence until the relevant block is finalized. Services may use their own deposit-crediting thresholds. In plain English: “submitted,” “included,” “successful” and “credited by a platform” are different stages. Where it appears: explorer status pages and deposit histories. Decision affected: if funds have not appeared, first check the transaction’s on-chain status and network, then check the receiving service’s current confirmation requirements. ^[5]

Token approval

Exact meaning: an ERC-20 approval authorizes another address, often a smart contract, to spend up to a specified amount of a token from the approving account. It is not the same operation as sending the token immediately. In plain English: approval grants permission that a later contract action may use. Where it appears: decentralized application prompts and explorer token-approval records. Decision affected: examine the spender, token and allowance before signing; an unnecessary or excessively broad permission increases exposure if the spender is malicious or compromised. ^[7]

Relationship Map: From ETH to a Verifiable Result

The chain can be shortened to: asset → selected network → signed transaction → gas-funded execution → block inclusion → txid-based verification. If the transaction calls a smart contract, contract logic sits between execution and the final state change. ^[6]

Do Not Confuse These Ethereum Terms

Ethereum and ETH

Ethereum is the platform and network; ETH is its native asset. The practical consequence is that “support for ETH” does not automatically mean support for every token, layer 2 or Ethereum-compatible network. Confirm the exact deposit or withdrawal network before sending.

Coin and token

ETH is native to Ethereum, while an ERC-20 token is represented by a smart contract. This distinction changes how a transfer is executed and what must be verified. For ETH, check the destination and network. For a token, also check the token contract and ensure the destination can receive that token. Token transfers still require ETH for gas when sent from a self-custody account. ^[7]

Asset and network

An asset is what you intend to move; a network is the system that processes and records the movement. The same asset name may appear on multiple networks or through bridged representations. Selecting the wrong network can prevent automatic crediting and may result in permanent loss or a recovery process that is unavailable.

Address and private key

An address is public receiving information. A private key is secret authorization data. Sending someone your address allows them to identify your account; sending them your private key allows them to control it. Never paste a private key into a field presented as an “address verification” step. ^[10]

Seed phrase and private key

A private key normally controls one account, while a seed phrase may derive multiple accounts and keys. Losing either can remove access; disclosing a seed phrase can expose a much wider set of accounts. Neither is a Memo, Tag, password-reset code or information required by a recipient. ^[4]

Gas and fee

Gas is the amount of computational work; the network fee is the ETH paid for the gas used at the applicable price. A high gas limit does not necessarily equal the final charge, but an inadequately low limit can make execution fail. A wallet’s fee estimate can also change before submission because network demand is not fixed. ^[8]

Network fee and exchange cost

An Ethereum network fee pays for blockchain execution. A quoted exchange amount may separately reflect the service’s current terms, available liquidity or execution conditions. Combining these under the word “commission” makes it difficult to identify why the received amount differs from an initial estimate. Review each displayed component before creating or confirming an operation; do not assume that an exchange rate includes every possible network or service cost.

Transaction and exchange order

A transaction is an on-chain signed instruction. An exchange order or application request may exist off-chain before any blockchain transfer is made. Creating an order does not prove that funds were sent, while a successful on-chain transaction does not necessarily mean that a platform has already matched, converted or credited it. Use the order identifier for the service process and the txid for blockchain verification.

Confirmation and success

A transaction can be included successfully while still producing an unintended result—for example, sending to the wrong address or granting approval to the wrong contract. “Success” means the network executed the submitted instruction without reverting; it does not certify that the instruction was wise, that the destination belongs to the intended party or that an off-chain service will credit it. ^[9]

Memo/Tag and Ethereum address

A Memo or Tag is not a replacement for an Ethereum address. Some custodial services use additional identifiers for internal account crediting, while others do not. Never invent one or copy it from a previous transaction. If a receiving service explicitly supplies additional deposit information, follow its current instructions exactly; otherwise, do not assume that a Memo or Tag is required.

Practical Example: Exchanging ETH Without Mixing Up the Stages

Suppose you want to exchange ETH through a service that currently supports ETH. Begin by checking whether the required direction and exact network are available; support for the asset does not imply that every pair, network or route is active.

1. Identify the asset. Confirm whether you hold native ETH or a tokenized or bridged asset with a similar name.
2. Check the source network. Open the wallet’s network view and verify where the balance exists. Do not infer the network from the 0x address format alone.
3. Review the service’s current route. Use the available ETH exchange direction only after confirming the accepted network, destination details and current operation terms.
4. Check verification requirements. Requirements can depend on the operation direction and the results of compliance checks. Confirm what is currently required before creating the request.
5. Create the request and copy fresh deposit details. Compare the asset, network and full address. Use a Memo or Tag only if the service explicitly provides one for that deposit.
6. Review the wallet transaction. Check the destination, amount and estimated network fee. If the wallet shows a contract interaction rather than a straightforward transfer, stop and determine why.
7. Sign without revealing secrets. A transfer requires a local signature, not disclosure of the seed phrase or private key.
8. Save the txid. Check it in an explorer for the network actually used. Confirm the status, receiving address, transferred asset and amount.
9. Separate blockchain completion from service processing. If the transaction is successful but the exchange request has not updated, compare the deposit requirements before considering another transfer.

Crypto transfers may be irreversible, and recovery from a wrong address, unsupported network or incompatible contract may be impossible. Phishing pages can imitate wallets, explorers and exchange interfaces, so obtain deposit details through the intended service session and verify sensitive actions in the wallet itself. Rules governing crypto services and taxation also differ between countries; check the requirements applicable to your location without treating this workflow as legal, tax or investment advice.

How to Recognize the Terms in a Wallet, Explorer or Documentation

• In a wallet: look for the selected network, sending account, destination address, asset, amount, requested action and fee estimate. A contract interaction may describe a function, approval or data request rather than only a recipient and amount.
• In a block explorer: search by txid or address. Common transaction data includes status, block, sender, recipient, value and gas information. Token activity may be displayed separately from the transaction’s native ETH value. ^[9]
• On a token page: distinguish the token’s name and ticker from its contract address. The contract address is the stronger identifier when similarly named tokens exist.
• In smart-contract documentation: identify whether an operation reads data or changes state. A state-changing action requires a transaction and gas; a read-only call made without changing state does not itself require an on-chain transaction from the user. ^[5]
• In deposit instructions: treat the asset, network, address and any explicitly supplied Memo or Tag as separate fields with separate purposes. Do not reuse old details without checking them again.
• In a transaction result: verify more than the status label. Match the network, sender, recipient, asset or token contract, amount and any approval or contract events to the action you intended.

Final Pre-Sign Checklist

• The asset is native ETH or the exact intended token.
• The sending and receiving networks match and are currently supported.
• The full recipient or contract address comes from a trusted, current source.
• Any Memo or Tag is used only when the recipient explicitly requires and supplies it.
• The wallet describes the expected action: transfer, approval or contract call.
• The account has enough ETH on that network for gas.
• The maximum fee and transferred amount are acceptable without assuming a fixed rate or confirmation time.
• No website, form or support agent has requested the seed phrase or private key.
• The txid will be saved and checked on the correct network’s explorer.

If any one of these checks fails, pause before signing. Ethereum will execute a validly signed instruction according to network and contract rules; it cannot determine whether the address, network or permission matches your original intention.