Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A node is a participating point in a network or system. In computer networking it is a connected device or endpoint; in a blockchain it is a running instance of client software; in a web document it can be an object in the DOM tree. What a node does depends on the context and, in blockchain networks, its protocol and configuration.

What does “node” mean?

“Node” is a general term, not the name of one specific device or software product. It describes a point that belongs to a larger connected structure. The National Institute of Standards and Technology’s NISTIR 8202 glossary describes a blockchain node as an individual system within a blockchain network. MDN uses the term for both network connection points and objects in a document tree.

That context matters: a router can be a networking node, an Ethereum client can be a blockchain node, and a page’s text can be a DOM node. These uses share the idea of a component within a connected system, but they do not share the same job or requirements.

What is a node in networking?

In networking, a node is a connection point in a network. MDN notes that a physical node is usually a device such as a computer or router. Depending on the network, nodes may act as endpoints that send and receive data, or help direct traffic between other devices.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
#1 Best Overall
Sale
Pearson Computer Networking, 8E
  • brand: Pearson
  • Computer Networking, 8e

For example, a laptop connected to a local network is a node, as is the router that connects devices or forwards their traffic. The word alone does not specify whether a node is a client, server, router, or another kind of equipment; its role comes from how it is configured and used.

What is a blockchain node?

A blockchain node is a computer running software for a particular blockchain and communicating with other computers running compatible software. Google Cloud defines a blockchain node as an instance of client software running on a computer in a distributed network where other computers run the same software. Ethereum.org similarly describes a node as an instance of Ethereum client software connected to other computers running Ethereum software.

Nodes help a blockchain operate without depending on one central computer. Depending on the network and setup, a node can receive and relay data, keep some or all ledger data, verify blocks and transactions, provide an application interface, or participate in consensus. These responsibilities are related but not interchangeable: connecting to peers does not automatically make a node a validator, and running a validator role does not by itself explain how much historical data the system retains.

What are the different types of nodes?

There is no single universal list of node types. Names vary by technology, and a node may be described by more than one attribute—for example, by how much data it keeps and whether it participates in consensus.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Type or context What it generally does Important distinction
Networking node Connects to a network as an endpoint or helps forward traffic; computers and routers are common examples. The word identifies a connection point, not a specific networking role.
Full or archival blockchain configuration Retains substantial blockchain data and can support verification against that data. Retention and verification behavior depend on the protocol and configuration; “full” and “archive” are not interchangeable guarantees across networks.
Lightweight or API-oriented configuration Retains less data or provides access through services or other nodes; an API-facing node can expose data and transaction functions to applications. How much it stores and what it can verify independently vary by implementation.
Relay or repeater node Forwards blocks or other network data to connected peers. Algorand documents repeater nodes as routing data to connected non-repeater nodes; this is a protocol-specific role.
Validator or consensus node Participates in a network’s consensus process when configured and eligible to do so. Algorand documents validator nodes as participating in consensus. The requirements and duties are defined by each protocol.
DOM node Represents a part of a web document, such as the document, an element, text, or a comment. It is an object in a document tree, not a networked computer.

Ethereum documentation also distinguishes node configurations by how much data they consume. Its categories and data-retention behavior should be understood within Ethereum, rather than assumed to apply unchanged to every blockchain. Likewise, Algorand’s repeater and validator labels describe roles in Algorand, not universal blockchain node classes.

What does a node do?

A node’s job depends on the system it belongs to. Common functions include:

  • Connect devices: Networking nodes provide endpoints for communication and may forward traffic.
  • Verify blockchain data: Ethereum nodes verify blocks and transaction data, according to Ethereum.org.
  • Store ledger data: A blockchain configuration may retain extensive history, a reduced dataset, or other protocol-defined data.
  • Relay information: Nodes exchange data with peers; Algorand repeaters are one documented example of a forwarding role.
  • Participate in consensus: Some configured nodes take part in the process a protocol uses to agree on network state.
  • Serve applications: A node can expose interfaces such as JSON-RPC or WebSocket endpoints so applications can read data, submit transactions, or interact with smart contracts. Google Cloud documents these as ways to work with blockchain nodes.
  • Represent a web page: DOM nodes let browser APIs and scripts work with a document’s structure and content.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How should you compare blockchain node options?

Before choosing a node setup, identify the network and the task you need it to perform. Compare options on the following points; the answers are protocol- and deployment-specific.

  • Data retained: Does it keep extensive history, a reduced dataset, or rely on another service for some information?
  • Verification responsibility: Which blocks or transactions can it check itself, and what data or other services does that depend on?
  • Network role: Does it mainly relay data, participate in consensus, or do both?
  • Application access: Does it provide the API or endpoint your software needs?
  • Operating demands: Check the selected protocol’s documentation for hardware, storage, bandwidth, setup, and ongoing maintenance requirements. There is no general hardware specification for all nodes.
  • Trust assumptions: Determine which data is checked locally and which services or other nodes the setup relies on.

These dimensions are more useful than choosing by a label alone. Two options both called “nodes” may keep different data, expose different interfaces, and have different verification or consensus roles.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Do you need to run your own node?

Not necessarily. If you only need to use an application, that application may connect to nodes operated by its provider or another service. Running your own node is more relevant when you want direct access to a network, need to make verification decisions locally, or intend to operate a role—such as a validator—that the protocol supports.

Decide based on the outcome you need, rather than the word “node.” If your goal is application access, confirm the available endpoint and what it lets the application do. If you want to verify data or participate in consensus, check the specific network’s rules and operating requirements first. Hardware, bandwidth, maintenance, and eligibility cannot be generalized across protocols.

Is a node the same as Node.js?

No. “Node” can also refer to Node.js, a JavaScript runtime, but that is a separate meaning from a networking or blockchain node. MDN identifies Node.js as one of several contexts in which the word appears. When a page or product says “node,” use its surrounding context to tell whether it means a connected device, a blockchain client, a DOM object, or the runtime.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.