VigiChain
07

Testnet

The network is live on testnet.

VigiChain runs today as a multi-node testnet. Figures shown across this site are clearly marked as mock or devnet values and carry no real-world worth.

Network statusTestnet active · Mainnet locked

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 it.

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 free relay lets home operators behind NAT still peer. No company servers, no paid infrastructure.
Start a testnet node
# 1) Download the binary for your OS from the node repo's Releases,
#    then verify it against SHA256SUMS.

# 2) Linux — join the testnet (real PoW, tvigi1 addresses, no real value):
chmod +x vigichain-node-linux-x86_64
VIGI_NETWORK=testnet ./vigichain-node-linux-x86_64 start

# or mine testnet VIGI from block zero:
VIGI_NETWORK=testnet ./vigichain-node-linux-x86_64 mine

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.

Network status · live probe

vigichain.org/rpc
PROBING

Querying the public RPC gateway…

Networkvigichain-testnet
Height
Best block
Validators
ConsensusHybrid PoW + BFT
PQ signaturesML-DSA-65 / SLH-DSA
MainnetLOCKED
RPC latency
Last probe17:16:09

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.

Execution layer · live probe

vigichain.org/rpc
PROBING

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 probe17:16:09

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 dApp

Network details

Network name
Vigi Chain Testnet
Chain ID
0x56494754 · 1447642964
Currency symbol
VIGI
Decimals
8
RPC URL (public)
https://vigichain.org/rpc
RPC URL (local node)
http://127.0.0.1:28721
Block explorer
https://vigichain.org/explorer
P2P port
28719
Bootnodes
seed-1.vigichain.org:28719

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.

EVM wallet — read & identity

  1. 01Add the network (button above). Your node must be running, or use a public seed RPC.
  2. 02Prove control of your EVM address: personal_sign the binding challenge from the node.
  3. 03Submit an EVM_BINDING signed by your post-quantum key to link the two addresses.

BTC wallet — identity binding

  1. 01Derive your Vigi ↔ BTC alias with the CLI.
  2. 02Sign the BTC binding challenge with your Bitcoin key.
  3. 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.

POST /api/faucet  ·  vigi_requestFaucet

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
01

Status: active

A live testnet exercises mining, transactions, propagation and the full validation path.

02

Mock data

Until a trusted public RPC is exposed, explorer values are illustrative mock data — never presented as mainnet.

03

Future integration

The architecture is ready to connect a real RPC and explorer without redesign.

04

Mainnet is locked

Mainnet unlocks only after validation, security testing and vulnerability closure.

Sovereign post-quantum network for verified value.

A sovereign post-quantum network for verified wrapped assets, self-custody, sealed receipts and financial control. Testnet active; mainnet locked until validation is complete.