VigiChain
04

Vigi Autonomous Escrow

VIGI stays locked until a proof says otherwise.

The economic primitive the rest of the ecosystem draws on: value released when an agreed condition is demonstrated cryptographically, with nobody in the middle deciding whether it was met. The foundation is already in consensus and audited. The general condition — one that is neither a signature nor a block height — is the piece still missing.

Network statusTestnet active · Mainnet locked

The ten layers

Every layer, and what it is today.

05
01

A provider was paid for a proved period, and the rest stayed locked.

Two of three — a client, a provider, and an adjudicator who is never asked and never holds anything. The client locks the contract plus the gas of every movement it will take; a custody proof goes on the chain; the payment is computed against that proof and comes to exactly contract ÷ periods, to the vix. What the release leaves behind goes back under the same lock, which is what makes a contract a sequence of periods instead of one payment. A period already paid cannot be claimed again, and a release that never settled leaves the period claimable — a signature that failed to arrive must not cost a provider work it has already done. Carried out against a real chain on 2026-08-19; on the public testnet the rule switches on at block 8,000.

02

Two parties can lock value and release it — and this is what it took.

A policy can require one post-quantum signature, an M-of-N quorum, or a height timelock wrapping either, and `vigichain escrow` makes that usable by people instead of only by tests: build the policy, lock the VIGI, then release it with a file that travels between the parties, each signing on their own machine. Nobody holds anybody else's key, and every signer recomputes what they are authorising before they sign it. Proved on a live chain rather than in a fixture: value locked under a 2-of-3, refused with one signature, released with two, and the remainder re-locked under the same policy — which is how a contract pays for one period and keeps the rest. Getting there meant closing four separate places where a release consensus accepts was refused by everything around it, one of which would have stopped the chain outright. On the public testnet the rule switches on at block 8,000.

03

A condition that is not a key and not a clock.

Everything above releases on who signed or on when. Machine-to-machine contracts need a third kind: release on a proof that a service was delivered — storage still holding data, a computation performed, an API available. That is an extension to an audited primitive rather than a new subsystem, which is why it is stated as partly built and not as designed.

04

One escrow, reused by every layer.

Storage payments, Proof of Recovery, compute, availability, dataset delivery and software delivery all need the same thing: value that cannot move until evidence exists. Building that once, in the layer everything shares, is what stops each service from inventing its own half-trusted settlement.

05

Objective proof only.

Autonomous escrow works where a condition can be demonstrated, not where it must be judged. Whether a file is still recoverable can be proven; whether a design is beautiful cannot. Disputes that need human judgement are outside this primitive on purpose — pretending otherwise would put an arbitrator inside a system built to remove one.

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→