Janzeer node 0.1.1 (mainnet)

Second mainnet release. Same network, same protocol: a 0.1.0 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

• Windows x86-64 bundle (janzeer-node-0.1.1-mainnet-windows-x64.zip, start.cmd)
• Raspberry Pi / Linux arm64 bundle (janzeer-node-0.1.1-mainnet-linux-arm64.tar.gz; 64-bit OS, Pi 3/4/5)
• Arch Linux package janzeer-node-bin (pacman -U, systemd unit, user janzeer, data in /var/lib/janzeer-node; PKGBUILD under packaging/arch/)
• Explorer pages carry their own titles

Fixed

• The bundle launchers now stop the embedded H2 database only after the node has written its clean-shutdown marker (DB_CLOSE_ON_EXIT=FALSE, AUTO_SERVER dropped). A node that was stopped cleanly skips the boot sweep and is back in a few seconds instead of about two and a half minutes. PostgreSQL deployments were never affected.

Upgrade from 0.1.0

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.1-1-x86_64.pkg.tar.zst && sudo systemctl restart janzeer-node.

SHA-256

8729fcb1e9f04e0df7d981f7dd481f71bf467f13e5fd808a8af3abbb46a087b5  janzeer-node-0.1.1-mainnet-linux-x64.tar.gz
18e703f2f7a5874e7589f227101b46d33703f0a286c48383611b6f173e612f0a  janzeer-node-0.1.1-mainnet-windows-x64.zip
a5b8e2ef44de871074ae91d45e7098fc986a52f928fac0a3ca2a9dca8825c165  janzeer-node-bin-0.1.1-1-x86_64.pkg.tar.zst
2b78e97c90e013973957a0675c6216f2119c1a0fbfd9ad344783a839814a25ce  janzeer-node-0.1.1-mainnet-linux-arm64.tar.gz

Verify with sha256sum -c SHA256SUMS (Windows: certutil -hashfile janzeer-node-0.1.1-mainnet-windows-x64.zip SHA256) before running. macOS builds follow.