Repository navigation
Janzeer node 0.1.2 (mainnet)
Third mainnet release. Same network, same protocol: a 0.1.0 or 0.1.1 node keeps working, upgrade when convenient.
- Network
janzeer, protocol 3.4.0, API 1.1.0 - Genesis hash
3a716783ee58bc56335aaede1d489eeda22cd7442c358f085a83213028b7782c - Native executables, no Java needed
New
- Sync progress.
GET /api/v1/info/syncreports the sync state, the committed height, how many blocks the running sync has downloaded and verified, the best known target height and the peer count. The explorer served by the node shows a banner with a progress bar while the node catches up, so a fresh node no longer looks frozen: it verifies a whole epoch before it commits the first block, which takes hours on a Raspberry Pi./actuator/healthcarries the same numbers.
Fixed
- A node restarted in the middle of its first sync could run out of memory while discarding the blocks it had staged, and then sit in PROCESSING forever without downloading anything (seen on a Raspberry Pi 3 with the default 256 MB heap). The staged blocks are now dropped with one statement, and any failure on the sync thread resets the node so the next check starts a fresh round.
Upgrade from 0.1.x
Stop the node, replace the bundle folder, keep your data/ folder (it holds config.json, your node identity), start again. Arch: sudo pacman -U janzeer-node-bin-0.1.2-1-x86_64.pkg.tar.zst && sudo systemctl restart janzeer-node. Do not restart a node that is still in its first sync unless you have to: a restart discards the staged blocks and starts the download over.
SHA-256
1092ea29749115ce03ec4edc9a1363a207be3771767a3e8d4187aaf478df037b janzeer-node-0.1.2-mainnet-linux-x64.tar.gz
5a8f2a49f8e59ff2f425f164ef1f285ee59526b33d65641f0a9188edebd010f8 janzeer-node-bin-0.1.2-1-x86_64.pkg.tar.zst
f535d3921ec6d8afe9107912f81877fb36f9034bdd02dabc0481b9423759d5a5 janzeer-node-0.1.2-mainnet-linux-arm64.tar.gz
Raspberry Pi / Linux arm64: janzeer-node-0.1.2-mainnet-linux-arm64.tar.gz (Pi 3/4/5, 64-bit OS). A Windows bundle follows as a separate asset.
Verify with sha256sum -c SHA256SUMS (Windows: certutil -hashfile <file> SHA256) before running.