Node Software
Specialisation is what makes the network scale
A specialised node layer carries the heavy work. A wide, open application surface sits above it, accessible to any builder without running infrastructure.
Who runs a node
Node software is for miners
In the Bitcoin white paper, a node is a participant that collects transactions into blocks, does the proof-of-work and extends the longest chain. On the BSV blockchain, that is still what a node is: node software is for miners.
Everyone else, from wallets and applications to exchanges and businesses, can confirm their own payments with Simplified Payment Verification (SPV), which the white paper sets out in section 8: "It is possible to verify payments without running a full network node." A copy of the chain that does not mine adds nothing to the network's security, so the white paper never asks every user to run one.
That is a deliberate difference from networks that expect everyone to run a full node. It keeps the node layer specialised and the application layer open, which is what lets the network scale.
SV Node and Teranode
Same protocol, same consensus rules, different engineering philosophy
SV Node
ProductionToday's network
SV Node is the production software carrying the BSV blockchain's mainnet today. Written in C++ and maintained by BSV Association, it is a monolithic full node handling transaction validation, block assembly, mempool management and state persistence on one machine. It supports massive block sizes, parallelised validation, detailed logging and the security controls required for enterprise use. A monolithic node scales by adding resources to a single server, and has taken the BSV blockchain into the thousands of transactions per second.
Teranode
Production (beta)Rolling out now
Teranode is the next-generation node software, written in Go as a distributed system of microservices. Transaction validation, block assembly, mempool management and state persistence each become independently scalable services, so capacity is added by adding servers. Where SV Node operates in the thousands of transactions per second, Teranode is engineered for millions.
| SV Node | Teranode | |
|---|---|---|
| Status | Production | Production (beta) |
| Language | C++ | Go |
| Architecture | Monolithic | Microservices |
| Transactions per second | Thousands | Millions |
| Repo | github.com/bitcoin-sv/bitcoin-sv | github.com/bsv-blockchain/teranode |
Participation
How to run your own node
Running a node is for miners. A production SV Node requires substantial storage (several terabytes; UTXO set alone in the hundreds of GB), best on high-performance SSDs. Initial sync from genesis takes days, and it needs continuous monitoring and security hardening. For everyone else, the node layer is infrastructure you use, not infrastructure you run.
| Development (regtest & testnet only) | Production minimum | Production recommended (STN minimum) | |
|---|---|---|---|
| Use | Follow the most-work chain and handle small volumes of other tasks, such as RPC requests | Handle a medium workload while staying in real-time sync with the chain tip | Handle a high volume of work, run with txindex enabled, or mine |
| Processor | 4 core, 8 thread | 8 core, 16 thread | 10 core, 20 thread or more |
| Memory | 16 GB RAM + 10 GB swap | 64 GB RAM + 64 GB swap | 64 GB RAM + 64 GB swap; ideally more RAM and less swap, keeping 128 GB in total |
| Internet | 10 Mbit+ up and down | 100 Mbit+ up and down | 1 Gbit+ up and down |
| Disk, pruned | 10 GB magnetic disk | 500 GB SSD | 1 TB SSD |
| Disk, unpruned | 20 GB magnetic disk | 16 TB SSD | 32 TB SSD |
These are the recommended requirements from internal testing, and they are expected to change as the network scales. From release 1.0.14, the prune settings can be used to fine-tune disk use. Miners should also make sure their nodes have the highest possible connectivity with other miners. Full system requirements
Docs