Vigi Data V2
A distributed data layer that keeps the data off the chain and keeps the chain as the root of integrity over it. Datasets, documents, artefacts, backups, models and application data stay with their providers; what the ledger holds is what makes them checkable — commitments, Merkle roots and proofs of possession.
Verify a file against the chain
The file stays on your device. Only its SHA-256 is sent.
Try it — the whitepaper this site publishes is anchored on the testnet. Download it, drop it above, and the chain answers. whitepaper (.md)
Anchoring a file
A proof is signed by the issuer, so it is made on the issuer’s own machine — never here, and never by a server holding a key:
vigichain utility anchor contract.pdf --type contract --version v1
Run the storage half yourself
Two programs, and neither is ours to run on your behalf: the client encrypts your file before cutting it into shards, and the provider holds shards it can never read. Both are built from the repository — there is no packaged release yet.
Store a file
Encrypted here, spread across independent providers, challenged periodically, rebuilt when one disappears. Four shards out of six bring the file back.
vigi-data put contract.pdf --providers http://a:9301,http://b:9301,http://c:9301,http://d:9301,http://e:9301,http://f:9301 vigi-data prove contract.pdf.vigi --beacon <hash of a recent block> vigi-data repair contract.pdf.vigi --replacements http://g:9301 vigi-data get contract.pdf.vigi --out contract.pdf
put writes a manifest and a key. The manifest is public and can be rebuilt from the chain and the providers; the key is the file. Nobody else holds a copy — not the providers, not us — so losing it loses the data.
prove takes a beacon because a challenge you pick yourself is not a challenge. Use a recent block hash. It ends by naming the shards that went unproven, rather than with a reassuring summary.
Be a provider
One process, one directory, one port. No account, no password, no database, no outbound connections. It binds to loopback until you decide otherwise, because exposing a storage daemon is a decision and not a default.
cargo build --release -p vigi-provider -p vigi-client vigi-provider --data ./vigi-shards --capacity-gib 200 --bind 127.0.0.1:9301 vigichain service publish --namespace VIGI_DATA_V2/PROVIDER_REGISTER --subject <provider id> --body provider.json
Registering puts a commitment on the chain, never a list of what you hold. What you hold is ciphertext cut into pieces too few to rebuild anything, and padding keeps the size of the original from being read off the shard.
What this does not do yet
Storing a file now writes the contract's on-chain record and hands you the one command that anchors it. What is still missing is settlement: payment against verified proofs is wired to neither program. So it stores, proves and repairs for real, and no provider is being paid for it.
The ten layers
A 1 GiB provider is registered on-chain and answers through the public Zotac seed. A client stored and recovered encrypted shards byte-for-byte through the public TLS endpoint. This proves the transport and one-provider storage path; three URL spellings reached the same machine, so independent-provider redundancy, Continuity and VPoR are not yet proven on the public testnet.
Data, commitments, proofs, availability, storage, payment and consensus are distinct problems, and systems that fuse them end up unable to change any one of them. Keeping them separate is what allows storage to scale, proofs to get cheaper and payment to be replaced, without a consensus change for any of it.
Fragmentation, replication, redundancy and encryption are the baseline, not an option: a storage provider stores encrypted fragments and can prove possession of them without ever being able to read them. This is a hard requirement of the design, because a provider that can read your data is a provider who can be compelled to.
Payment for storage runs through Autonomous Escrow against proofs of possession and, over time, Proof of Recovery — value that cannot move until the provider has demonstrated it is still holding what it agreed to hold. The economics and the verification are the same mechanism, not two systems that have to be reconciled.
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.
