Install

How TSUNAGI is deployed today

Honest status: TSUNAGI runs as a single operator-deployed installation on Cardano Preview, deployed from sha-verified bundles and run under the Guardian supervisor. A public one-command installer ships with the first public release — it will be announced here, and not before it's real. ← Docs

Prerequisites

A synced cardano-node (Preview) as the local peer (e.g. 127.0.0.1:6000).
Pool keys: VRF skey, KES skey, operational certificate.
The TSUNAGI binary bundle (Zig 0.16, ReleaseSafe) + its published sha256.

Deploy (the real procedure)

Verified bundle → supervised launch

# 1. verify the bundle BEFORE anything touches the forge path
sha256sum tsunagi-node-<ver>.tar.gz        # must match published sha
tar -xzf tsunagi-node-<ver>.tar.gz
sha256sum tsunagi-node-<ver>               # must match published binary sha

# 2. snapshot the current binary into the rollback chain
cp ~/bin/tsunagi-node ~/.rollback/tsunagi-node-<prev>-$(date +%Y%m%d-%H%M%S)

# 3. stop, swap, verify, start UNDER supervision
guardianctl guard down                      # if already supervised
cp tsunagi-node-<ver> ~/bin/tsunagi-node
sha256sum ~/bin/tsunagi-node               # confirm install sha
~/start-relay-forge-guarded.sh             # env block + launch under guardiand

# 4. verify
guardianctl guard status                    # running, supervised pid, correct sha
# boot markers: OPCERT_PIN seq=0 · sigma_source=stake_source · MODE live

Environment (keys, opcert, LMDB, KES period) lives in the launcher's export block and is never modified by a binary swap. The Guardian supervisor is described in Guardian; day-to-day commands in Operations.

Roadmap

Today: sha-verified bundle + supervised launch (battle-tested — every canonical block was produced this way).
Planned: one-command install (guided + advanced modes) with published checksums and Guardian installed alongside the node.