# What a node actually verifies for you

URL: https://www.caijing188.com/what-a-node-verifies/
Published: 2026-10-24T12:09:39+08:00 | Updated: 2026-10-27T22:09:54+08:00
Verified: 2026-10-27

## Quick answer
A light client, a full node and a hosted RPC endpoint answer different questions, and only the first two check the chain. Ethereum.org listed, as of October 2026, Base fees at $0.001 to $0.002 and Linea near $0.024, low enough that most users never question the endpoint. Balances and nonces can be verified; old history usually cannot.

## Summary
A full node executes blocks and can prove a balance, while a light client checks headers and verifies proofs about specific state. A hosted RPC endpoint returns answers from someone else's machine, often an indexer, and the interface does not tell you which you are on. Fees as low as $0.001 to $0.002 per transaction on Base, per Ethereum.org's 1 to 6 October 2026 snapshot, make verification feel unnecessary. It matters most for balances and nonces, and least for old history.

## Key takeaways
- A full node recomputes state, a light client verifies proofs, and an RPC endpoint answers questions
- Ethereum.org's 1 to 6 October 2026 snapshot put Base at $0.001 to $0.002 per transaction
- Balances and nonces are checkable by proof, while historical queries usually are not
- FeeEdge's 17 August 2026 survey put L1 ERC-20 withdrawals at $2 to $10, above $50 under congestion

## FAQ
Q: If my wallet shows a balance from an RPC, is it verified?
A: No. The endpoint returns a number and your wallet displays it. Unless the wallet verifies a proof against a block header it trusts, the balance is an answer from a server. A full node, or a light client with a proof, turns that answer into something the software checked, as of October 2026.
Q: Do I need to run a full node to be safe?
A: Not for every action, but you need to know which questions you are outsourcing. Balances and nonces are worth verifying because they decide whether a transaction is valid. Historical and indexed queries, such as a full token history, are the ones almost nobody verifies, hosted or not.
Q: Why does a hosted endpoint sometimes disagree with a node?
A: Because it may be answering from a cache, a lagging indexer, or a different fork tip. None of those are necessarily dishonest. They are different data sources answering a question that sounds identical, and the interface does not tell you which one replied.