VigiChain
07

The layers

A small core, and everything else wrapped around it.

VigiChain is built so the base chain stays small enough to audit and long-lived enough to trust: a capability only enters consensus when every node on earth must run it to decide whether a block is valid. Everything above wraps the chain instead of enlarging it. This page names each layer and says, for each, whether it is running today, partly built, or a design with no code behind it — including the ones that are still empty.

Network statusTestnet active · Mainnet locked

The ten layers

Every layer, and what it is today.

02
01

The smallest set of rules everyone must agree on.

Proof of work proposes blocks, a UTXO ledger settles them, and every signature that moves value is post-quantum. The chain state is a UTXO set, not a table of account balances, so validation stays deterministic, traceable and parallelisable later. Testnet is live and anyone can join with one command; mainnet stays locked until independent validation closes. Nothing else belongs at this level — that restraint is the feature.

02

One question decides where a feature lives.

Does every node need to run this rule to decide whether a block is valid? If not, it stays outside — and if commitments, proofs, RPC, an external protocol or a verifiable service can do the job, that route wins. VigiChain is not trying to become a storage chain, an AI server, a cloud provider or a marketplace written into consensus. It is the cryptographic and economic root those things can be built on.

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.