Janzeer blog ยท
Why no staking: validators, the 2,000 JNZ deposit and rotating seats
Second article of the series. How a Janzeer validator gets in, what the deposit buys, how seats are assigned, and how the launch nodes work themselves out of power.
Yesterday's article gave the shape of Janzeer: a block every 15 seconds, final in one block, a fixed supply, no staking. Today is about the part people ask about first. If nobody stakes, who validates, why would they, and what stops a thousand fake nodes from taking over?
What a stake does, and what it costs
Proof-of-stake solves one problem well: it makes identities expensive. A validator must lock coins, so an attacker needs a large share of the coins to hold a large share of the votes. The side effects are the part I do not like.
The lock earns yield, so validating becomes an investment product. Weight follows wealth: whoever holds the most coins casts the most votes and earns the most new coins. Smaller holders delegate to pools, and a few pools end up casting most votes on most chains. Unbonding periods, slashing of the stake, and reward-sharing contracts pile on top, and each one is a place where things go wrong.
Janzeer keeps the useful part, expensive identities, and drops the rest. A validator identity costs 2,000 JNZ, once, and that payment buys exactly one seat with exactly one vote. It earns nothing by itself.
Getting in: one transaction
A validator is a node plus one registration transaction. The node syncs the chain, then its operator sends a registration carrying the node's public key, a fixed fee of 3 JNZ, and a deposit of 2,000 JNZ. There is no application, no vote, no approval by anyone. If the transaction is valid, the node is registered.
The deposit goes to the treasury, the key-less address that pays block rewards, and it never comes back. Not when the validator leaves, not when the network grows, not on request. That is the whole Sybil guard: a thousand fake validators cost two million JNZ, paid into the pot that rewards the honest ones. I will say plainly that this guard is softer than a large stake or proof-of-work. It is sized for a small network of operators who run nodes because they want to run nodes.
A registered node joins the validator set at the next epoch boundary. The explorer's validators page shows it as pending until then.
Seats, epochs and rotation
Time on Janzeer is divided into epochs of 17,000 blocks, about three days. At each boundary every node computes the same new validator set from the chain's state, and a special genesis block records it. From then until the next boundary the set is frozen: slot after slot, the right to propose a block goes round the set in a fixed order, and the set votes.
The set has at most 21 seats. While fewer validators are registered, everyone who is registered and awake has a seat. When more register than there are seats, the longest-registered validators keep their seats and five of the seats rotate, epoch by epoch, through a standby bench of up to a hundred, in registration order. No lottery, no weight, no bidding: the order you joined is the order you serve.
Two things remove a validator from the set. If it stays silent on its assigned slots for an epoch, it is dropped at the next boundary; it keeps its registration and comes back when its node is healthy. And a validator can leave on purpose with an exit transaction, which takes it out of the schedule at the next boundary instead of degrading the chain for three days. Either way the deposit is gone.
What the validator earns
Every block pays its producer 10 JNZ from the treasury, plus 80 percent of the fees in that block. The other 20 percent of fees returns to the treasury. Nothing is shared with anyone, nothing is claimed later, nothing is paid for merely being registered. Rewards are for work, measured one block at a time.
The reward halves roughly every year, and the treasury is finite. In the long run a validator lives on fees, which is how it should be on a chain with a fixed supply.
With seven validators today, each produces one block in seven, about 820 blocks a day. That is the current arithmetic, not a forecast; it changes with every validator that joins, and JNZ has no price to multiply it by.
Misbehaviour
The one thing a validator can do to hurt the chain, besides being offline, is to vote twice in the same slot for two different blocks. Every node keeps one vote per validator per slot per voting stage. A second, conflicting vote is itself the proof: any node that sees it wraps it into a slashing transaction, and the chain records the offense. After two proven offenses the key is banned permanently. Whoever reported it receives a 5 JNZ bounty from the treasury.
There is no slashing of a stake because there is no stake. The penalty is the seat and the 2,000 JNZ that bought it.
The launch problem: anchors that phase themselves out
Every new chain faces the same awkward moment: at block one there is nobody to validate but its creator. Janzeer launched with three anchor nodes run by the project, and they are privileged in exactly one way: an anchor cannot be dropped for downtime. The number of privileged anchors is written into every epoch's genesis block, so any node can reconstruct it.
That privilege is designed to expire. Once enough independent validators have proven themselves, meaning they produced blocks in each of the last two epochs, one anchor loses its privilege per epoch. A demoted anchor is not switched off; it keeps validating like any other registrant and can be dropped like any other registrant. The rule never lets the healthy set fall below four, and if the independent set collapses later, dormant anchors re-engage. The anchors are scaffolding, and the chain takes the scaffolding down on its own schedule.
Today the project still runs five of the seven validators: the anchors and a fifth node. The other two are a Raspberry Pi 3 in my home and a balenaFin board at a friend's. I want that ratio to turn around, and the mechanism to turn it around is already live.
If you want a seat
Running a validator takes a machine with 2 GB of memory and a public port, the node bundle from the validators page, and the 2,003 JNZ for the registration. For the first ten outside operators the project covers that amount through a grant, paid from the ecosystem wallet to the address you name, until the first of January 2027 at the latest. One grant per operator, and the project's own nodes do not count. The operator guide walks through the whole thing; a Raspberry Pi has done it, so a small VPS will.
Tomorrow: what happens inside those 15 seconds. The two-phase vote, why a committed block is final, and what the chain does when a validator is missing.
Janzeer is built with AI assistance (Claude Code); every number here is from the live chain and the protocol facts in the public documentation, and the text is mine. JNZ is the network's unit, it is not listed anywhere, and nothing in this series is financial advice.
Also published on: