Module 5 — Nodes and Validators: Who Actually Runs the Network

·course·2026-06-11

A blockchain has no central server. So who keeps it running? The answer is nodes — the many computers that store the ledger and follow the rules. This module explains nodes, their types, and the special role of validators.

5.1 What is a node?

A node is simply a computer running the blockchain's software and participating in the network. Each node:

Holds a copy of the ledger (the chain of blocks).
Receives new transactions and blocks from other nodes.
Checks that everything follows the rules.
Passes valid information along to its neighbors.

The network is the collection of nodes. There's no building you can point to and say "the blockchain lives there" — it lives across all of them at once. This is what makes it resilient: shut down some nodes, and the rest carry on.

5.2 Types of nodes

Not all nodes do the same amount of work. The common types:

Full node: stores a complete, up-to-date copy of the ledger and independently verifies every rule. Full nodes are the backbone of the network's integrity — they don't take anyone's word for it; they check everything themselves.
Light node (lightweight client): keeps only a small slice of data and relies on full nodes for the rest. This is what runs on resource-limited devices — for example, the wallet app on your phone is essentially a light client. It doesn't store the whole chain; it asks full nodes for what it needs.
Archive node: a full node that also keeps the complete historical state of the chain at every past point in time. It's heavy and storage-hungry, used for deep historical queries, explorers, and analytics.

Analogy: a full node is someone who owns the entire library and re-reads every book to check it; a light node is someone who just phones the library to ask one fact; an archive node is the library that also keeps every previous edition of every book ever printed.

5.3 What is a validator, and how is it different from an ordinary node?

Here's the key distinction. Most nodes only verify and relay — they check that incoming blocks are valid and pass them on, but they don't create new blocks. Validators are the special nodes that actually produce and confirm new blocks, deciding which transactions get written into the permanent record and in what order.

In short:

Ordinary node: "I'll check what you send me and keep an honest copy."
Validator: "I'll create the next page of the ledger, and the others will check my work."

Every validator is a node, but not every node is a validator. Becoming a validator usually requires meeting the network's consensus rules — in PoW you need mining power, in PoS you need a stake, and in PoA you need to be an approved, identified party.

5.4 Who becomes a validator in PoA, and how?

This is where Proof of Authority (Module 4) and validators meet. In a PoA network, validators are not random or anonymous. They are explicitly approved, known entities — chosen because their real-world identity and reputation can be trusted and held accountable.

The process typically looks like this:

A candidate validator's identity is established and vetted.
The network's existing authority adds them to the approved validator set.
They take turns producing blocks according to the network's rules.
If a validator misbehaves or goes offline, they can be removed from the set.

This is exactly why PoA suits private and consortium networks — and ecosystems that run their own chain. In a setting like the Tupic ecosystem, the parties operating the network are known and accountable rather than an anonymous global crowd, which is the defining feature of PoA.

5.5 The role of validators in network health and security

Validators carry a lot of responsibility. Their honest behavior keeps the whole system trustworthy:

Ordering transactions fairly — preventing manipulation of who gets processed first.
Excluding invalid transactions — refusing double-spends or improperly signed transfers.
Keeping the network live — producing blocks reliably so transactions keep confirming.
Maintaining accountability — in PoA especially, their known identity means misbehavior has real consequences.

A network's trustworthiness ultimately rests on its validators. In open networks that trust is enforced by cost or stake; in PoA networks it's enforced by identity, reputation, and the power to remove bad actors. Either way, validators are the engine room — and understanding their role is the difference between seeing a blockchain as "magic" and understanding how it actually stays honest.

Key takeaway: Nodes store and verify the ledger; full, light, and archive nodes do so at different depths. Validators are the special nodes that create new blocks. In PoA, validators are approved, identified parties whose reputation keeps them honest — the model used by private, consortium, and ecosystem chains.

⬅ Previous: Module 4 — Consensus Mechanisms & PoA | Next: Module 6 — Smart Contracts ➡

Tupic Academy — Education series. Free to learn, no login required.