Node and CLI binaries, version 0.2.1. Every archive holds the node and the
tenzro command line. Each platform has a CPU build or a GPU build; pick the one that
matches the machine. The manifest is signed with the Tenzro release key.
Linux and macOS (x86_64 and arm64). It picks the right archive for the machine, verifies the
signed manifest and the archive before it installs anything, and needs no sudo. Add -s -- --dry-run
after sh to see what it would choose without changing anything.
curl -fsSL https://downloads.tenzro.com/install.sh | sh
Windows (PowerShell):
irm https://downloads.tenzro.com/install.ps1 | iex
Then run tenzro; the first run takes you through setup. Run the installer again to update. The scripts are covered by TLS only; their hashes are in
install.sh.sha256 and install.ps1.sha256, and the manual,
verify-it-yourself steps are below and at Verify your download.
Each archive holds tenzro-node, the tenzro CLI and,
on Linux, the installer tenzro-node-install. The Windows build needs the NVIDIA driver and the
CUDA 13 runtime; cuDNN 9 as well for ONNX models on the GPU.
tar -xzf tenzro-node-linux-x86_64-cpu.tar.gz
cd tenzro-node-linux-x86_64-cpu
./bin/tenzro-node hardware
./bin/tenzro setup
curl -O https://downloads.tenzro.com/SHA256SUMS
curl -O https://downloads.tenzro.com/SHA256SUMS.sig
curl -O https://downloads.tenzro.com/tenzro-release.pub
cosign verify-blob --key tenzro-release.pub --insecure-ignore-tlog=true \
--signature SHA256SUMS.sig SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missing
--insecure-ignore-tlog=true.
MANIFEST.txt and matrix.json record how each
archive was built; the software bill of materials and the build provenance
(an unsigned in-toto statement; the signed object is SHA256SUMS) are in the same folder.
Built from commit 3870736ac9e05276ee286100ac0bcfa456b3f7c0.
The signature is a classical ECDSA P-256 signature from a hardware-held key; a post-quantum signature is planned as a follow-up.
Steps for Linux, macOS and Windows: Verify your download.
Source is Apache-2.0 licensed.
On this release a new node joins by block replay from genesis: start it with the network's genesis file and it replays the chain from block 0, then follows the network. Joining from a snapshot arrives in an update.
tenzro-node --genesis genesis.toml
Running a node needs a TPM 2.0, or a Mac with a Secure Enclave, for its keys. A genesis
validator needs its own TPM 2.0 or Secure Enclave; a machine whose keys are in another machine's TPM joins after
genesis with tenzro validator register --tpm-key-holder. Steps:
Getting started.