Node infrastructure
Validator and worker nodes we operate
Alongside the client work, LEAD NODE runs nodes on public blockchain networks. It is the same operational discipline as the infrastructure we run for clients, with one difference: on a public network, how well you run it is a matter of public record.
A validator securing the Polkadex mainnet, a Substrate-based exchange with an on-chain order book. Its performance is visible on the public explorer, not asserted by us.
See the nodesarrow_forward
Two worker nodes on the Subsquid Tethys testnet, serving indexed blockchain data to the decentralised network that queries it.
See the nodesarrow_forwardRationale
Why a software company runs validators
Uptime nobody takes on trust
A validator that misses blocks is penalised in public, on chain, where anyone can check. It is the least forgiving reference we could offer for how we run infrastructure.
The same discipline, higher stakes
Key management, patching, monitoring and recovery are the same practices we apply to client systems. On a validator, getting them wrong costs real money immediately.
Hands on the actual stack
Running nodes keeps us current with the tooling rather than reading about it. What we learn there is what we bring to infrastructure work for clients.
Networks we have run before
Nodes we operated in the past and have since retired. Retiring a node is not a verdict on the network or on us: projects and priorities simply moved in different directions over time. They are listed for the record, not as running infrastructure.
Run the way everything else here is run
Hardware-key access, no password logins, encrypted disks and monitored hosts apply to these nodes as much as to client systems.