Janzeer blog ยท
One native binary: a Layer-1 node on a 2 GB VPS and a Raspberry Pi 3
Fifth article of the series. What it takes to run a Janzeer validator, why the node ships as a single native binary, and what the smallest machines taught us about it.
The last article explained why a Janzeer block is final once five of the seven validators have committed it. That raises the practical question: what does it take to be one of those seven?
The answer we aimed for from the start: a machine you already have. Not a rack, not a cloud account with a monthly bill in three digits, not a staked fortune. Today five validators run together on one rented 2 GB server, and two run on single-board computers in people's homes, one of them a Raspberry Pi 3 from 2016.
One file, no runtime
The node is written in Kotlin on Spring Boot: a peer-to-peer layer, the consensus engine, a database, a REST and JSON-RPC API, and the block explorer's web pages. A normal Java service like that needs a Java runtime and starts in tens of seconds.
Janzeer ships it as a GraalVM native image instead. The whole node is compiled ahead of time into one executable file of about 250 MB. There is nothing else to install: no Java, no database server (it brings an embedded database, or uses PostgreSQL if you have one), no container runtime. On the 2 GB server it starts in about 3 seconds; on the Pi 3 in about 30.
The download page has the same node for Linux x64, Linux arm64 (Raspberry Pi and other boards), Windows, an Arch Linux package and a Docker image. Every release carries a SHA256SUMS file signed with the project's key, so you can check that what you downloaded is what was released before you run it.
What running one looks like
- Download the bundle for your machine and verify the signature.
- Unpack it and run
./start.sh. The node creates its own identity, connects to the network and synchronises the chain from block one, checking every block itself. - When it reports
SYNCHRONIZED, it is a full watch-only node: it follows and verifies the chain, and its API answers your wallet or your scripts. - To validate, open the P2P port and send one registration transaction with a one-time 2,000 JNZ deposit, as described in the article about validators. The node joins the set at the next epoch boundary, about three days later.
The bundle also contains update.sh, which checks for a newer signed release and installs it, and jz, the command-line client, so ./jz node status tells you how the node is doing.
Why the binary matters on small machines
Memory decides what fits. A Java process grows its heap towards a share of the machine's physical memory unless you stop it; five of them next to a database would not fit in 2 GB. The native image starts small, its heap is capped at 256 MB, and its code pages are shared between processes. On the server, five validator nodes, PostgreSQL, the explorer, a Telegram game and a mail server share 2 GB. Before we rented that server, we proved it on a desktop by running the same binaries inside a memory cage of the same size for six hours.
The Pi 3 has 1 GB, of which 905 MB are usable. A synced node sits at about 370 MB there. That leaves room, but not much, and the board found every place where the node used memory carelessly.
What the smallest machine taught the node
Running on a 1 GB board turned up problems that a big server hides:
- A cleanup step loaded 287 MB of staged blocks into a 256 MB heap when a sync was restarted. On the server nobody noticed; on the Pi the sync thread died. The cleanup now deletes in the database without loading anything.
- Temporary files went to
/tmp, which on Raspberry Pi OS lives in RAM. A bulk database statement wrote 405 MB there. The node now keeps its temporary files on its own disk. - An unclean stop costs a long check at the next boot, because the node re-validates its last two epochs when it cannot prove it was stopped cleanly. On the server that took 2.5 minutes, on the Pi 22. The node now writes a marker on every clean shutdown and skips the check when the marker matches.
Every one of these became a fix in the node, released for everyone, not a special Pi build. The full story, with the numbers, is in the Raspberry Pi article.
What the operator learns
Some lessons have nothing to do with code. Use a proper power supply: an under-powered Pi drops its Wi-Fi without a word, and a validator that is silent for hours loses its seat. A board without a real-time clock boots with the wrong time after a power cut, and a node does not produce blocks until its clock is correct, because slots are assigned by time. And restart a validator right after its own block, not in the middle of its turn.
The server side has its own story: running the whole network on one 2 GB VPS, what broke in the seven-day acceptance test before launch, and how upgrades now restart the validators one by one so that no block is missed.
Why it is worth it
A network whose validators need a data centre ends up run by data centres. A network whose validators run on a Pi in a living room can be run by anyone who cares to. Today the chain is at block 248,850, with seven validators. The grant programme pays the 2,000 JNZ deposit for the first ten outside operators, and the first application arrived this week.
Next: non-custodial by design, or how keys are derived and why a Janzeer address is not an Ethereum address.
Janzeer is built with AI assistance (Claude Code); every number here is from the live chain and the project's own release notes and incident reports, and the text is mine. JNZ is the network's unit, it is not listed anywhere, and nothing in this series is financial advice.