VigiChain
09

Proof of Recovery

Prove it can be rebuilt — without shipping it to find out.

Part of Continuity, and its sharpest claim. The useful proof is not that a provider says it still has your file: it is a periodic demonstration that the resource can actually be reconstructed — fragments present, redundancy sufficient, reconstruction possible, integrity intact — without transferring the whole dataset just to check.

Network statusTestnet active · Mainnet locked

The ten layers

Every layer, and what it is today.

04
01

Would it come back today? Asked of the providers, answered on the chain.

The strong claim is now a command anyone can run and an event anyone can read. A stripe is drawn from the chain's own tip, reconstructed from a quorum, and checked against the shards that were not used to reconstruct it — a few kilobytes, not the dataset. A recovery that would fail is published under a different name from one that would succeed, so anyone watching for failures sees them without reading a single body. On 2026-08-19 the whole cycle was carried out against a real node — the events published, accepted by consensus, read back, and the derived state rebuilt from nothing but the chain. What is still missing is people: the public testnet has no participants in this layer yet.

02

Holding a fragment is not holding the file.

A provider can prove it holds the bytes it was given and still be unable to return your data: shares lost at other providers, redundancy silently eroded, an encoding whose parameters no longer reconstruct. Proof of possession answers a question about one provider. Recovery answers the question the owner actually has.

03

A check that costs less than the loss.

A recovery test that requires downloading everything is a test nobody runs often enough to matter. The design target is a sampled, challenge-based demonstration whose cost is small and whose failure is loud — because the value of this layer is entirely in how frequently it can be afforded.

04

Payment conditioned on still being recoverable.

Once recovery is demonstrable it becomes an escrow condition, and storage stops being a subscription paid on trust: value releases as the provider keeps proving the resource can be rebuilt, and stops when it cannot. That is the mechanism this layer exists to enable.

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→