What Is Node in Crypto?

A node is a computer running blockchain software that maintains a copy of the chain's state and relays transactions across the network. Every wallet, exchange, validator, and DeFi app ultimately depends on nodes somewhere. Node types differ by what they store and verify: full nodes (all state), archive nodes (all historical state), light nodes (headers only), and validator nodes (additional consensus duties).

Also known as: full node, crypto node, blockchain node

Ask Stingray anything about Node

Types of nodes

  • Full node — verifies every block and transaction; stores recent state. On Ethereum, ~500GB disk currently. Can serve RPC queries for recent state.
  • Archive node — stores all historical state since genesis. On Ethereum, ~15TB+ disk. Required for querying historical balances or contract states.
  • Light node / client — stores only block headers; relies on full nodes to provide proofs for queries. Low resource, but trust-minimized only with cryptographic attestations.
  • Validator node — a full node plus the consensus layer participating in block proposal/attestation. On Ethereum, validator + execution client is the full stack.

Running a node serves different purposes:

  • Self-sovereignty — querying your own node means you’re not trusting a third-party RPC provider (Alchemy, Infura) for your balance or transaction data.
  • Validator duties — any PoS validator needs access to both a consensus node and an execution node.
  • Development / indexing — block explorers, MEV searchers, and DeFi indexers typically run dozens of archive nodes.

Running a node today

For Ethereum:

  • Hardware — modern NVMe SSD, 32GB+ RAM, consumer CPU. A Rock5, a Mac mini, or a cloud VPS works. Full-node baseline: ~$1,000 hardware + $50/mo electricity.
  • Software — execution client (Geth, Nethermind, Erigon, Besu) + consensus client (Prysm, Lighthouse, Teku, Nimbus). Diversity matters — using a minority client is good for network resilience.
  • Bandwidth — ~1-2 TB/month up/down is typical. Home internet works; symmetrical connections are preferable.
  • Sync time — snap sync takes ~1-2 days to first block; historical sync for archive is weeks.

Most DeFi users don’t run their own nodes. RPC providers (Alchemy, QuickNode, Infura) offer free tiers sufficient for retail; paid plans cover heavy use.

Risks and considerations

  • RPC provider risk — if you use Alchemy or Infura, they can censor or misreport. Almost always they don’t; in a future world with more regulatory pressure, they might. Running your own node is the structural defense.
  • Light client trust — light clients with solid cryptographic verification (Helios, Portal Network) are safer than simple API queries.
  • Node operator fraud — a malicious node operator running a validator can be slashed, but clever multi-chain operators have targeted nodes hosting only-slightly-tracked chains.

For most users, running a full node isn’t necessary but is a meaningful privacy-and-sovereignty upgrade. Wallet apps like Rabby and MetaMask support pointing at a local RPC endpoint; once configured, every transaction flows through your own infrastructure rather than a third party’s.

Related terms