{{ screenTitle }}

{{ screenSub }}
RC
Supply-chain compliance
9 suppliers · 4 active requirements · last sync 2 min ago
STATE
{{ s.label }}
{{ s.value }}
{{ s.sub }}
Supplier network
{{ l.label }}
{{ mapSvg }}
Live verification feed
LIVE
{{ networkIcon }}

No suppliers connected yet

Create a compliance requirement and invite your suppliers. Their proofs appear here as verifiable nodes — no raw data ever leaves their systems.

{{ emptyCta }}
RESOLVING PROOF STATES…
{{ st.num }} {{ st.label }}

Choose a compliance standard

The standard defines the schema your suppliers prove against.

Define the assertion

State what must be true, in plain language. Suppliers prove this holds — without revealing the underlying figures.

Assertion · {{ reqStandardName }}
assert {{ assertion }}
{{ infoIcon }} The assertion compiles to a zero-knowledge circuit. Suppliers run it locally against their own data; VeriProof only ever sees the boolean result and its proof.

Proof validity & cadence

How long a proof stays valid, and how often suppliers must re-attest.

Proof expiry
Re-attestation cadence

Review & publish

Publishing invites suppliers to attest. They receive the circuit spec — never a request for raw data.

{{ r.k }} {{ r.v }}
{{ shieldMiniIcon }} Circuit groth16 · bn254 will be generated and pinned on publish.
{{ reqProgressLabel }}
{{ lockIcon }}Hash-chained · tamper-evident
SeqTimestamp (UTC)EventActorEntry hash
{{ r.seq }} {{ r.ts }} {{ r.event }} {{ r.actor }} {{ r.hash }}
{{ auditFootnote }}
SIMULATE
{{ verdictIcon }}
Verification result
{{ verdictText }}
{{ verdictDesc }}
Assertion
{{ proofAssertion }}
Cryptographic receipt zk-SNARK
{{ r.k }} {{ r.v }}
Trust boundary
{{ eyeIcon }}Proven · public
{{ checkMini }}{{ p.t }}
{{ lockIcon }}Stayed private
{{ dotMini }}{{ p.t }}
Never transmitted. Never stored. Provably excluded from the proof.
{{ l.icon }} {{ l.t }} {{ l.tag }}
{{ eyeIcon }}
Public claim
{{ provenCount }}
facts revealed
vs
{{ lockIcon }}
Sealed inputs
{{ privateCount }}
datasets withheld
PROVEN → {{ proofAssertion }}
disclosedcryptographically hidden
Incoming attestation requests
Acme Industries is asking Helix Materials to prove 3 assertions. You reveal nothing but the result.
{{ q.icon }}
{{ q.name }}{{ q.cat }}
{{ q.assertion }}
Due {{ q.due }} · cadence {{ q.cadence }}
{{ q.status }}
{{ st.num }} {{ st.label }}

Connect a data source

VeriProof reads your data locally to build the proof. The connection stays on this machine.

{{ lockIcon }}Connection is local-only — credentials never reach VeriProof servers.

Map fields to the assertion

Tell the circuit which columns feed each input. These mappings stay local.

Circuit inputYour column
{{ m.input }} → {{ m.col }}▾
{{ genIcon }}

{{ genTitle }}

{{ genDesc }}

{{ genStage }}{{ genPct }}
{{ shieldMiniIcon }}Your data never leaves this machine
{{ g.mark }}{{ g.line }}
{{ genAction }}
{{ bigCheck }}

Proof submitted

Acme Industries received your proof and verified it in 1.2s. Helix Materials now shows as Verified for ISO 14064-1.

proof_hash  0x7c4e…a9f1
anchor      eth:0x3a…22e
verified    true · 1.2s