The layers
VigiChain separates what every node must execute from what only some participants need. A capability enters the consensus layer when there is a hard technical reason for every node on earth to run it, and lives outside it otherwise. That line is what keeps the base chain small enough to audit and old enough to trust. This page maps the five layers and says, for each one, what is running today and what is a design with no code behind it yet.
Proof of work proposes blocks, a UTXO ledger settles them, and every signature that moves value is post-quantum. Nothing else belongs here. The chain state is a UTXO set — not an account balance map — so validation stays deterministic, traceable and parallelisable later. Testnet is live and anyone can join it with one command; mainnet stays locked until independent validation closes.
Documents, credentials, licences, software releases, updates, API calls, node attestations and threat reports are anchored as commitments the chain carries and verifies. It never decides whether something is TRUE: it proves existence, integrity, origin and how a thing changed between two states — and it can prove that without publishing the content itself. The site calls this Vigi Passport; it is the verification layer, and it is built.
Vigi Wallet holds keys post-quantum and never lets them leave the background process; VigiScan reads the chain in the open; VigiBank shows on-chain capital without custody; VigiRail carries institutional payments and can be joined and used on the testnet today. Each says its own state on its own page, including what it refuses. None of them is a reason to change the consensus layer.
The design covers data availability, proof of recoverability and distributed compute that returns verifiable results — with the heavy bytes deliberately outside the chain, because the base layer should store only what is cryptographically necessary. There is no code for any of it. Not a module, not a stub. It is written here so the shape of the plan is public, and so nobody mistakes a plan for a product.
One primitive underneath all of it: VIGI locked until a previously defined condition is demonstrated cryptographically, then released without an intermediary. Storage, recovery, compute, availability, datasets and software would all settle through the same mechanism rather than each inventing its own. It has no implementation yet, and it is the keystone — the service layer cannot be paid for until it exists.
Every addition answers the same questions before it is written: what problem it solves, whether it must be inside the core, what attack surface it adds, what it costs to run, which invariants it touches, how it is tested and how it is reverted. When the choice is between more complexity in consensus and a verifiable layer outside it, the outside wins unless the security argument says otherwise. VigiRail is the working example: the chain already knows how to carry and commit it, and no network has switched that on.
Sovereign post-quantum network for verified value.
Post-quantum cryptographic security software: a sovereign network that strengthens custody, settlement and identity — verified assets, self-custody, sealed receipts. Testnet active; mainnet opens when independent validation supports it. Built in layers, each labelled.
