VigiChain Node — Public Testnet

Run a node on the VigiChain public, post-quantum test network. This repository distributes the ready-to-run node binary and the instructions to operate it. It does not contain source code — it is the official node build, published so anyone can join the testnet and help harden the network toward an honest mainnet.

Testnet only. VIGI on the testnet carries no real value. Mainnet is locked in the software and stays locked until an external security audit and sustained burn-in. Running a node today makes you a founding operator.

• Website: https://vigichain.org
• Explorer: https://vigichain.org/explorer
• Wallet: https://vigichain.org/wallet

---

What you get

• A single self-contained binary that mines and validates VigiChain testnet blocks.
• Post-quantum consensus end to end (ML-DSA-65 / SLH-DSA) — your node verifies every block for itself.
• Zero premint, no allowlist. Testnet VIGI is only mined, from block zero, on the same terms for everyone.

Requirements

• 64-bit Linux or Windows (x86-64), a modern CPU, ~1 GB free disk to start.
• Outbound internet. For inbound peering, allow TCP 28719 (or run behind the free relay — see Peering behind NAT).

Download & verify

Download the binary for your OS from the Releases page, then verify its checksum against SHA256SUMS:

# Linux
sha256sum -c SHA256SUMS 2>/dev/null | grep vigichain-node-linux
chmod +x vigichain-node-linux-x86_64

# Windows (PowerShell)
Get-FileHash .\vigichain-node-windows-x86_64.exe -Algorithm SHA256

Verify the signature (recommended)

A checksum alone does not prove who built the binary. Each release ships a .sig next to every binary, made with the VigiChain release key. Verify it with minisign or the compatible rsign2:

VigiChain release public key:

RWQItT0J/YGNHI45GYmzWqVLUP+fMp5GXIbKxjp7eH/l7vZLfhv7KUsa

# minisign — save the key line above as vigichain.pub (prefixed with a comment line):
minisign -Vm vigichain-node-linux-x86_64 -p vigichain.pub

# or rsign2 (no key file needed — paste the key inline):
rsign verify -P RWQItT0J/YGNHI45GYmzWqVLUP+fMp5GXIbKxjp7eH/l7vZLfhv7KUsa \
  -x vigichain-node-linux-x86_64.sig vigichain-node-linux-x86_64

A binary is authentic only if verification succeeds against that key. VigiChain is sovereign: releases are signed by a single UTXO Labs key — but you never have to trust that signature. Integrity is meant to be verified, not trusted:

• the release key is held offline / in hardware, so it cannot be stolen from a build host or a compromised account;
• builds are reproducible — rebuild from the audited source commit and confirm the binary matches bit-for-bit;
• each release carries GitHub build-provenance tying the binary to that exact commit and CI run (gh attestation verify).

Sole authority, zero required trust in a third party.

Run a testnet node

# Linux
VIGI_NETWORK=testnet ./vigichain-node-linux-x86_64 start

# Windows
$env:VIGI_NETWORK = "testnet"
.\vigichain-node-windows-x86_64.exe start

Your node creates a persistent identity once at <data_dir>/node_key.json (owner-only permissions; the secret key is never printed). Testnet addresses start with tvigi1.

Mine testnet VIGI

VIGI_NETWORK=testnet VIGI_MINER_ADDRESS=<your tvigi1 address> \
  ./vigichain-node-linux-x86_64 mine

Configuration (environment variables)

Variable	Purpose	Default
VIGI_NETWORK	testnet (this repo) / devnet (local)	testnet
VIGI_NODE_KEY_PATH	node identity keystore path	<data_dir>/node_key.json
VIGI_MINER_ADDRESS	tvigi1… address that receives mined rewards	none
VIGI_BOOTNODES	comma-separated peers, or local for a private lab	network default
VIGI_DATA_DIR	chain + keystore storage	platform data dir

Mainnet will not start: it is refused at compile time until launch, by design.

Peering behind NAT

Home operators behind a router can peer without opening ports by pointing the node at the public WebSocket relay published at p2p.vigichain.org (a transport relay only — every node still validates all blocks locally). See the website for the current relay endpoint and status.

Updating

Download the newer release, verify its checksum, and restart with the same VIGI_DATA_DIR. Your chain data and identity are preserved.

Support & security

Questions and vulnerability reports: see SECURITY.md.

License

Proprietary — see LICENSE. You may run this binary to operate a VigiChain node. You may not reverse engineer, modify, or redistribute it. © UTXO Labs. All rights reserved.