Veraq · Developers
Build on the open record.
The developer surface for Veraq. Read the seven record entities, the commit-reveal-v1 mechanism, and a REST API generated from the published contracts. The promise is checkability: every record carries its open-record reference, and every implementation is verifiable against the published golden vectors. You don’t have to trust it — you can check it.
Verify it yourself
Verify
The mechanism is committed to the open record before a wave runs and is provable after. Run the golden vectors before anything else — a green run is the source of truth behind the verification badge.
verify it yourself✓ verifiable
# Don't trust the box — open it. Verify before you read another line.
npm test # or: cargo test · pytest — runs the published golden vectors
# Every vector is committed before a wave runs, and provable after.Start here
Coming with the live API
Provisional
The Quickstart, SDKs, the open-record explorer, the validator portal, the contracts reference, and the changelog are specified in the brand system and ship with the live API and record backend — which this open documentation repository does not contain. They are marked provisional in the navigation until that backend lands.