UPGRADE to go-zenon v0.0.10 ASAP

Development
1

Node operators: upgrade to go-zenon v0.0.10 and keep your restore point indefinitely

We intend to carry out the community spork renewal in the coming days. Please upgrade your Pillars, and public nodes to go-zenon v0.0.10 before the spork is issued. Nodes running v0.0.8 or v0.0.9 need this upgrade. This is a private release reviewed by me, @digitalSloth and Mr. Stockholmz. @sol and @georgezgeorgez have followed the work and bugs. Release and download details.

The instructions below use nomctl, the node management app I built, to install the signed release and automatically create a protected restore point. Please keep that restore point indefinitely so we have a recovery option if a coordinated rollback becomes necessary.

These steps are for an existing node on Debian/Ubuntu with systemd, using an amd64 or arm64 processor. If your node uses custom service names or installation/data paths, check the nomctl configuration before proceeding.

  1. Install or update nomctl on your node server.

    Install the download and signature-verification tools:

    sudo apt-get update
sudo apt-get install -y curl ca-certificates gnupg

    If nomctl is not installed:

    curl -fsSL https://raw.githubusercontent.com/0x3639/nomctl/main/install.sh | sudo bash

You can audit the code and review the docs here: https://nomctl.0x3639.com/

If you already have nomctl:

sudo nomctl upgrade

Check the installed version:

nomctl --version

Use nomctl v0.15.3 or newer, which includes the clearer restore-point prompts.

  1. Start the signed node upgrade.

    Run:

    sudo nomctl upgrade-node --signed --version v0.0.10

    Alternatively, open sudo nomctl, choose Install & upgrade → Upgrade a node from signed release, and select v0.0.10.

    Before installation, nomctl explains that a restore point is required. It automatically saves your current chain data and installed znnd, including the znnd version and commit when available, plus its SHA-256 checksum. This gives you matching data and node software to restore together.

    Wallet and configuration backups are separate from this restore point.

  2. Choose “Indefinite” and confirm the upgrade.

    When asked how to keep the restore point, select:

    Indefinite — keep until I delete it

    Please retain this point throughout the fork and afterward until we confirm it is no longer needed. Indefinite points are excluded from automatic cleanup and bulk pruning.

    nomctl verifies the release signature and checksum and checks available disk space before stopping the node. It then copies the existing data, installs v0.0.10, and restarts the service before finishing archive compression.

    Keep the terminal open until the operation reports that both the upgrade and restore point are complete. If either reports an error, keep the recovery files and ask for help here.

  3. Check the upgraded node and locate your restore point.

    For the standard installation paths:

    sudo /usr/local/bin/znnd version
sudo nomctl status

    Confirm the installed version reports 0.0.10, the service is active, and synchronization is progressing.

    In sudo nomctl, open Backups & recovery → Manage restore points. Locate the completed point labelled Before upgrade to v0.0.10, confirm it is indefinite, and note its ID and timestamp. Its saved znnd is the version you were running before this upgrade.

If the fork fails and a coordinated rollback is announced, use the following procedure. A single node falling behind does not by itself mean the fork failed.

  1. Run sudo nomctl.
  2. Choose Backups & recovery → Restore from restore point.
  3. Select the completed restore point created immediately before your v0.0.10 upgrade. Check its timestamp and saved znnd version.
  4. When asked “Also revert znnd to the version saved in this restore point?”, select Yes — restore chain data and saved znnd (recommended).
  5. Review and confirm. nomctl verifies the saved files, stops the node, restores the matching data and znnd, and starts the service again.
  6. Run sudo nomctl status and check the installed znnd version again. Follow the rollback announcement’s guidance for verifying the intended chain.

Use Restore from restore point for this rollback. Restore from backup restores data only and leaves the installed znnd version unchanged. Also, nomctl upgrade --rollback rolls back the nomctl app, not your node.

Keep the restore point after recovery. If restoration fails, preserve the reported recovery files and share the error here before taking further action.

A node that follows the old chain after the spork needs a different recovery procedure. The existing renewal discussion explains resyncing on v0.0.10 and checking momentum hashes, since matching heights alone do not prove nodes are on the same chain.

Please reply once your node is upgraded and your indefinite restore point is confirmed.