01
Status: active
A live testnet exercises mining, transactions, propagation and the full validation path.
09
Testnet
The network is live on testnet.
VigiChain runs today as a public testnet that anyone can join from their own machine. Be plain about its shape: the chain is currently produced by a single anchor node, and the network publishes that figure itself — it improves the moment a second producer joins. Figures shown across this site are clearly marked when they are sample values and carry no real-world value.
Network statusTestnet active · Mainnet locked
01
Status: active
A live testnet exercises mining, transactions, propagation and the full validation path.
Founding node operators
The network is the people running it.
The testnet software is live and the network is opening now. There is no company server behind it — it grows only as independent operators come online, each mining and validating for themselves. Run a node and you don’t use the network, you found.
The fairest possible start
Zero premint. No allowlist. A public GPU bootstrap where every miner shares the same target. VIGI can only be mined — from block zero, on the same terms for everyone.
Post-quantum, proven by you
Your node validates every ML-DSA-65 / SLH-DSA block for itself. Running it under real conditions is the adversarial burn-in that stands between the testnet and an honest, audited mainnet.
Your machine, zero cost
The node runs on hardware you already own and keeps consensus local. A Tor route lets home operators behind NAT peer without opening a port, using a Tor proxy on their own machine. No company servers, no paid infrastructure.
Public testnet — VIGI here carries no real value. Mainnet stays locked until an external security audit and sustained burn-in. Founding operators are how the network earns that GO.
Run a node
One command, and your computer is part of the network.
A web page cannot install software on your machine — none can, and any page that claims otherwise is lying to you. What it can do is hand you the exact command, already verified, so joining is a copy, a paste and one confirmation.
Linux, or Windows inside WSL
curl -fsSL https://vigichain.org/join.sh | bashWindows (PowerShell)
irm https://vigichain.org/join.ps1 | iexOn Windows the supported path is WSL (wsl --install -d Ubuntu), and the script uses it when it finds it. The native Windows build works — the network anchor runs on Windows — but every instruction another operator will ever give you assumes Linux, and on Windows those differences are yours to absorb.
What the command does, in order
- 01Downloads the current node release from GitHub.
- 02Checks its SHA-256 against the release checksum file and its signature against the VigiChain release key. A binary that fails either check is deleted, not run.
- 03Installs it under your own home directory. No administrator rights, nothing outside ~/.vigichain, no service, nothing that starts by itself at boot.
- 04Creates your node identity and starts mining the testnet, using your CPU count minus one.
Undoing it. Delete ~/.vigichain and it is gone: binary, chain data and identity. Nothing else on your machine was touched.
If you have no mining hardware and just want to see it work
An ordinary laptop mines this testnet today. Difficulty is not a fixed schedule here: the network retargets every 60 blocks to hold a 30-second block, so it follows whatever hashrate is actually online. With a handful of nodes, a normal machine finds blocks. As more join, the target tightens for everyone — that is the mechanism working, not a door closing. Testnet VIGI is worth nothing, deliberately: what you are producing is evidence that the software survives real machines.
If you have a rig
Proof of work here is double SHA-256 over the block header, so CPU farms and GPU farms both apply and your share of the same 30-second slots simply grows with your hashrate. VIGI_MINING_THREADS pins the thread count instead of the default; VIGI_MINER_ADDRESS pays rewards to an address you control rather than the node identity. The testnet is where you measure your setup, your power draw and your uptime before any of it counts.
What changes when mainnet opens
On mainnet the first 1,000,000 VIGI are mined at the bootstrap target — deliberately easy, so ordinary hardware takes part in the start on the same terms as anyone else. Then difficulty does not jump: between 1,000,000 and 1,100,000 VIGI it doubles in sixteen steps, each small enough for real hashrate to follow, and after that the programmed difficulty applies and tightens in stages to a final phase that is hard on purpose. These are supply thresholds, not dates and not block numbers. Mainnet stays locked in the software until independent validation supports opening it.
Network status · live probe
vigichain.org/rpcPROBING
Querying the public RPC gateway…
Networkvigichain-testnet
Height—
Best block—
Validators—
Producing nodes—
ConsensusHybrid PoW + BFT
PQ signaturesML-DSA-65 / SLH-DSA
MainnetLOCKED
RPC latency—
Last probe—
This panel reads the network directly every 20s. Values are testnet only and carry no real worth. When the gateway shows a height, a node is genuinely serving it — when it doesn't, the panel says so rather than pretending.
Finality · live reading
vigi_getValidatorSetreading the network…
The set stopped being empty at height 4000, and the advisory round protocol now signs real quorum certificates with a post-quantum key over live blocks. It is still advisory: one bonded validator is not a committee, so chain selection remains pure proof of work and the consensus finalised height stays at genesis. Both figures above are read from the chain, not asserted here.
Execution layer · live probe
vigichain.org/rpcPROBING
Querying the execution layer…
Reserve invariant
L2 supply = VIGI locked on L1
Rollup—
State root—
L2 supply—
Locked on L1—
Batches—
Sequencer—
FinalityOPTIMISTIC-V1 · REEXEC-V1 · STARK-V1
Challenge window—
RPC latency—
Last probe—
The execution layer is a post-quantum rollup: L2 balances are native VIGI, backed 1:1 by VIGI locked on the L1 — the reserve is verifiable on-chain, not a claim. Withdrawals are trustless (optimistic challenge window or instant REEXECvalidity), and a fraudulent batch is provably reverted. This panel reads it every 20s and says offline when no node answers rather than pretending.
Fastest way to try it
No setup. Open the VigiSwap dApp (or VigiWallet), connect, claim test VIGI from the faucet and transact — every transfer is signed with a post-quantum key for you.
Open the VigiSwap dAppNetwork details
Network name
Vigi Chain TestnetChain ID
0x56494754 · 1447642964Currency symbol
VIGIDecimals
18RPC URL (public)
https://vigichain.org/rpcRPC URL (local node)
http://127.0.0.1:28721Block explorer
https://vigichain.org/explorerP2P port
28719P2P bootstrap
tor://2k2us2joevlvnja7i74dbfre3krmwmi3cbft5pvz4t3rtguzoha7xzyd.onion:28719,seed-04.vigichain.org:28719Tor SOCKS proxy (yours)
127.0.0.1:9050Mining payout address
VIGI_MINER_ADDRESS=<your VigiWallet address>Add the network to an EVM wallet
For reading balances and binding your identity. Adding the chain lets MetaMask read the testnet; moving value still happens through the post-quantum path below. Decimals is 18 because that is the unit the eth_* view answers in, and the only value MetaMask accepts for a native currency; the chain itself counts in vix, with 8, and the gateway converts.
EVM wallet — read & identity
- 01Add the network (button above). Your node must be running, or use a public seed RPC.
- 02Prove control of your EVM address: personal_sign the binding challenge from the node.
- 03Submit an EVM_BINDING signed by your post-quantum key to link the two addresses.
BTC wallet — identity binding
- 01Derive your Vigi ↔ BTC alias with the CLI.
- 02Sign the BTC binding challenge with your Bitcoin key.
- 03Submit the binding, signed by your post-quantum key.
Run a node (become a peer)
The testnet lives as long as peers are online. Run the node from your shell to join it, expose your own local RPC and help keep the network alive.
cargo run --release -- start
Get test VIGI
Request testnet coins from the faucet — they carry no real value.
curl -s -X POST https://vigichain.org/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"vigi_requestFaucet","params":["<your address>"]}'1 VIGI per request, once an hour per address and per IP.
Security note: VigiChain deliberately rejects raw secp256k1 (MetaMask) and ECDSA (BTC) value transactions — consensus requires a post-quantum signature. EVM/BTC wallets are for reading and identity; value moves through VigiWallet, the VigiSwap dApp or the native path. Testnet only. Mainnet stays locked until validation is complete.
04
02
Live figures
The explorer and VigiScan read the public gateway at vigichain.org/rpc. When no node answers, the page says so and falls back to clearly marked sample values instead of inventing numbers.
03
Public gateway
A JSON-RPC endpoint at vigichain.org/rpc that any wallet, indexer or script can read without running a node. Height, block time, hashrate, mempool and validators all come from it.
04
Mainnet is locked
Mainnet unlocks only after validation, security testing and vulnerability closure.
Sovereign post-quantum network for verified value.
Post-quantum cryptographic security software: a sovereign network that strengthens custody, settlement and identity. Testnet active; mainnet opens when independent validation supports it. Ten layers, each with its own page and its real state on it: three running, two half-built, five written but not yet on the network.