Janzeer node 0.1.14 — network: mainnet (linux x64)
=====================================================================

This folder is a complete Janzeer node: one native executable, its runtime libraries, the network's public
genesis (genesis.json) and a launcher. No Java, no database server and no configuration are required.
Documentation: https://janzeer.org/docs (Node Operator Guide).

1. Verify the download
   Linux/macOS:  sha256sum -c SHA256SUMS      (or: shasum -a 256 -c SHA256SUMS)
   Windows:      certutil -hashfile janzeer.exe SHA256   and compare with SHA256SUMS
   The values published on https://janzeer.org/validators must match.

2. Start
   Linux/macOS:  ./start.sh
   Windows:      start.cmd
   Docker:       see docker-compose.yml in the Docker distribution
   The node creates ./data (ledger + your node identity in data/config.json), connects to the seed peers,
   syncs the chain and serves the explorer + API on http://localhost:7019 . Sync status:
       curl -s http://localhost:7019/api/v1/info      -> "syncStatus":"SYNCHRONIZED" when caught up
   Requirements: 64-bit linux, 1 GB RAM free, 20 GB disk, an NTP-synchronised clock (block production halts
   if the clock is off by more than 250 ms).

3. Two ways to run
   WATCH-ONLY  (default) — you just started one. It follows the chain, serves the explorer and the API,
               and never produces or votes. No inbound port is needed: the node dials out to its peers.
   VALIDATOR   — the same node, registered on-chain:
               a) open the P2P port (default 9199/tcp) to the internet when you can, so other nodes can dial
                  you directly (a node behind a home router still validates over its outbound connections);
               b) read your node key:  curl -s http://localhost:7019/api/v1/info   -> "nodeKey": "02…"
               c) from any Janzeer wallet (web wallet / mobile app), Validators -> Register, paste the node
                  key and pay the one-time deposit (2000 JNZ, non-refundable) plus the fee (3 JNZ);
               d) the node joins the active set at the next epoch boundary and starts producing.
               Run EXACTLY ONE node per key — two nodes with the same data/config.json get slashed for
               equivocation.

4. Back up
   data/config.json is your node identity (validator key + seed phrase). Copy it somewhere safe and keep it
   secret. The ledger itself (the rest of ./data) can always be resynced from the network.

5. Upgrade
   The node checks once a day whether a newer release exists (https://downloads.janzeer.org/node/latest.json,
   notification only: it never downloads or installs anything). A newer release shows up as one warning line
   in the log, a notice at the top of the explorer and in  curl -s http://localhost:7019/api/v1/info/update .
   Opt out with --node.update.enabled=false appended to the launcher.
   Linux/macOS:  ./update.sh          downloads the new bundle, verifies the project's minisign signature on
                                      its SHA256SUMS and the archive checksum, keeps ./data, swaps the files,
                                      restarts the systemd service if that is how the node runs.
                 ./update.sh --check  only reports;   ./update.sh --rollback  restores the previous version.
                 Needs minisign (apt / pacman / brew install minisign). Release signing key (minisign, public):
                     RWQBrkWzg4V5n5wUBa9GNPpa95Z7WFT2EY5QrabMv/DP+KG+gJsPIgdr
                 The same key is printed on https://janzeer.org/validators — compare them.
   Windows:      stop the node, unpack the new zip over this folder (keep data\), compare SHA256SUMS, start.
   Arch Linux:   pacman -U the new package.
   Every release lists the protocol version in VERSION; peers on another protocol version disconnect you
   with "protocol version mismatch" in the log — upgrade when you see it. A protocol bump needs every
   validator to restart together: read the release notes before running update.sh on a validator.

6. Tuning (environment variables, see the top of start.sh / start.cmd)
   JANZEER_REST_PORT, JANZEER_P2P_PORT, JANZEER_ROOT_NODES, JANZEER_DATA_DIR, JANZEER_JAVA_OPTS.
   PostgreSQL instead of the embedded database:
       DB_URL=jdbc:postgresql://localhost:5432/janzeer DB_USERNAME=janzeer DB_PASSWORD=… ./start.sh
   Linux service: janzeer-node.service (instructions inside the file).

7. If the node refuses to start with "GENESIS MISMATCH"
   The genesis.json in this folder describes another chain than the one in ./data (for example a bundle
   of another network started on a mainnet data directory). Use the matching bundle, or move ./data away to resync.

8. Command line: jz
   The bundle may carry jz, the Janzeer command-line client (open source, https://github.com/janzeerOrg/janzeer-cli):
       ./jz node status            this node: version, sync, health, update availability
       ./jz node update            exit code 10 when a newer release exists; --run executes ./update.sh
       ./jz node logs -f           follow the log
       ./jz info · ./jz block tip · ./jz wallet new · ./jz send …     the chain and a local encrypted wallet
   It talks to http://localhost:7019 with  --profile local  (jz config init writes the profiles).

Files: janzeer (executable) · jz (command-line client, optional) · lib*.so|*.dylib|*.dll (runtime libraries, keep next
to the executable) · genesis.json · start.sh|start.cmd · janzeer-node.service · VERSION · LICENSE.txt · SHA256SUMS · README.txt
