VigiChain
05

Vigi Provenance

Where a thing came from, step by verifiable step.

Provenance chains evidence so an artefact can be traced back through the states it passed through: source, dataset, process, model, execution, output. Each step is anchored by Witness and linked cryptographically to the one before it, so the chain of custody of a digital object is itself checkable.

Network statusTestnet active · Mainnet locked

The ten layers

Every layer, and what it is today.

04
01

On the public testnet: the provenance of this release, checkable by anyone.

Two artifacts and one derivation were published to the public chain on 2026-08-19 — the pinned dependency set the build consumed, the recipe that was followed, and the step that links them to the binary. The step's subject is the binary's own SHA-256, so nothing has to be taken on trust: hash Cargo.lock and docs/REPRODUCIBLE_BUILD.md out of the repository, hash the binary you downloaded, and compare. The publishing key asked the faucet for its gas like anyone else.

02

Models, datasets, builds, documents.

An AI model whose training data is attested, a software build traceable to the commit and the toolchain that produced it, a dataset whose transformations are each recorded, a document whose every revision is anchored. The demand is the same everywhere: prove the history, without publishing the contents.

03

Links are commitments, not consensus rules.

A provenance edge is evidence referencing evidence. No node needs to understand a pipeline to decide whether a block is valid, so the chaining lives above consensus and inherits its guarantees from the Witness records it points at. The core does not grow to accommodate it.

04

It records the path, not the merit.

A verifiable history proves that specific inputs existed and that a specific process was identified. It does not prove that the process was appropriate or the output good. Provenance narrows where trust has to be placed; it never removes the need for judgement about the work itself.

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.

Read the Architecture→Explore the Network→