Vigi Witness
Witness is the layer everything else here is built on: it commits evidence about an event, a state or a process to the chain — hashes, Merkle roots, attestations, verifiable timestamps, signatures — while the content stays wherever its owner keeps it. Nine kinds of proof are carried and validated by consensus today.
The ten layers
Security and integrity proofs, node attestations, software releases, updates tied to a registered release, licence state, proofs of a critical API call, wallet and signing risk, document proofs, and threat events. Each is a transaction payload the network validates by rule — not a note in a database somebody could edit afterwards.
A commitment shows that something existed at a point in time, that it is intact, and who committed it. It cannot show that what was said about it is correct — no cryptography can. Stating that limit is part of the product: a proof layer that implies more than it demonstrates is worse than none.
What is published is a commitment, not a document. A hospital, an auditor or a manufacturer can anchor evidence about a record without the record leaving their systems, and a verifier who is later given the original can check it against what the chain has held since the moment it was written.
Every node must run these rules to decide whether a block is valid, so this is one of the few capabilities that belongs in the core. Everything above Witness — provenance, process, data, escrow — consumes it from outside and adds nothing to what all nodes must execute.
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: four running, six still a design.
