VigiChain
08

Vigi Continuity

Not that something was stored. That it is still there.

Continuity is about digital survival over long periods: proving that specific resources remain existent, available, intact and recoverable, for the infrastructure, software, datasets, companies and autonomous systems that depend on them being there in ten years — not on a receipt from the day they were uploaded.

Network statusTestnet active · Mainnet locked

The ten layers

Every layer, and what it is today.

04
01

The check that catches silent rot — now run against real providers, and published.

The sampled recovery check runs against live provider daemons: it draws a stripe from a value nobody chose, reconstructs it from a quorum, and compares it against what the other shards hold. One command asks it, and the outcome is published as an event. Killing a provider moved the answer to degraded and named the shard, while the survivors were still proving custody perfectly. 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

A backup nobody has ever restored.

Most data loss is not dramatic. It is a backup that silently stopped, a provider that quietly reduced redundancy, an archive whose format nothing can read any more. Each is discovered at the one moment the data is needed. Continuity moves that discovery forward by making the check continuous instead of hypothetical.

03

Existence, availability, integrity, recoverability.

Four properties, checked repeatedly over time and anchored so the history of checks is itself evidence. A resource that has been demonstrably recoverable every month for five years is a different claim from a provider’s statement that it has been backed up, and the difference is the entire point of the layer.

04

Anything expected to outlive its operator.

Critical infrastructure, long-lived software, public datasets, corporate records with statutory retention, and AI agents whose state has to survive the machine it ran on. The common thread is a dependency on something remaining available long after everyone who set it up has moved on.

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→