$VAN is not live. Every section below is written in the future tense and describes designed function.
Why the network needs an asset at all
Vangrid sells data whose value depends entirely on whether a buyer can believe it was captured where and when it claims. That requirement produces three constraints that a centralised stack does not satisfy:- Authenticity cannot rest on Vangrid’s word. A buyer evaluating crowd captured data has to be able to verify it without trusting the party selling it.
- Settlement has to clear in minutes, in any jurisdiction, at amounts below a dollar. No banking rail carries that profile.
- Provenance has to be anchored where no party to the transaction can rewrite it.
Verification collateral
Capture authenticity is the network’s core problem, and it is the token’s primary function. Automated checks at ingest catch the cheap attacks: replays, duplicates, captures whose camera and location signals contradict each other. They cannot resolve the harder cases, and a central review team is both a bottleneck and a single point of trust. Verification is therefore delegated to independent operators who put capital behind their judgement. The mechanism:- Operators stake $VAN to enter the verification set. The stake is the collateral behind every attestation they sign.
- Captures are sampled and assigned pseudorandomly. An operator cannot select which captures to review, and a contributor cannot select the operator who reviews theirs.
- Operators sign an attestation of authenticity. The attestation is attached to the capture’s provenance record and travels with the observation through the API.
- An attestation that disagrees with the resolved outcome costs the operator part of the stake. Sustained disagreement removes the operator from the set.
- Failing to act on assigned work carries its own penalty. Idle collateral does not accumulate anything.
- Queries that require the highest assurance route fees to the operators who verified the observations returned.

