Skip to content
Trust / verification

Don't trust. Verify.

Everything VEILOPS claims can be checked without asking us. This page lists each check, what it proves, and what it does not.
not auditedNo independent cryptographic review has been performed yet. The checks below are evidence, not an audit.
01

Reproducible build

in CI on every commit

Anyone can rebuild the release packages from a tag and get byte-identical tarballs. The script installs strictly from the lockfile, then runs typecheck, lint, all tests and the independent verifier, then prints SHA256SUMS.

git clone https://github.com/veilops-protocol/veilops && cd veilops
nvm install && nvm use       # Node pinned in .nvmrc
bash scripts/reproduce.sh    # compare dist/SHA256SUMS with the release

The website bundle itself is not bit-for-bit reproducible because Next.js embeds build ids, so it is excluded from the checksums.

02

Test vectors + a second implementation

two implementations agree

veilops-range-v1.json fixes the protocol: 7 commitments, 3 Fiat–Shamir challenges, 16 range-proof cases (10 deliberately broken), 10 policy-proof cases (6 broken) and 4 full records, each with its expected verdict.

Reference

TypeScript, @noble/curves. Runs in the browser and in npm test.

Independent verifier

Python standard library only: its own ristretto255, hash-to-curve and Ed25519, checked first against the official RFC 9496 and RFC 8032 vectors.

python3 verifiers/python/veilops_verify.py test-vectors/veilops-range-v1.json

Both implementations were written by this project, so this shows the specification is precise and consistent. It does not replace an outside review.

03

Solana devnet anchors

6 anchors on devnet

Verified sample records are anchored with SPL Memo transactions carrying veilops:<version>:<proofId>:<sha256(record)>. A daily workflow re-reads every transaction from a public RPC and checks that the memo matches the published record, that the published key signed it, and that the record still verifies.

cluster
devnet (test network, no real value)
memo program
MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr
npx tsx scripts/devnet-verify.ts   # re-check every anchor yourself

This is devnet only. There is no mainnet deployment and no on-chain verifier program yet.

04

Build provenance

from v0.1.1

Release files are built by GitHub Actions and carry a signed artifact attestation (Sigstore). The attestation proves which workflow run, repository and commit produced a file, so nobody can swap in a hand-made tarball unnoticed.

gh attestation verify veilops-proof-engine-0.1.1.tgz --repo veilops-protocol/veilops
05

Signed commits

from v0.1.1

Commits and tags on main are signed with the maintainer's SSH key and show Verified on GitHub. The project is maintained pseudonymously, so this key, not a name, is what ties every change to the same maintainer.

maintainer
signing key
SHA256:0q/tLTLWz3mdlXFnfCcJbDYeJ7nHnGu37TaBa/h96m8

The initial import on 2026-11-20 predates signing and is unsigned. Full history is in the changelog.

07

Independent review

not started

The scope, the questions for the reviewer and the known limitations are public in docs/audit-scope.md. When a review happens, the report will be published unedited, with the reviewer's name, dates and the commit reviewed.