Select a stakeholder role and a vehicle scenario, then run the verification. See exactly which fields each role receives — and what stays hidden.
Verification Simulation
IDLE
SCENARIO:
VIN (public ledger)1HGBH41JXMN109186
EN-1
Engine Node
ready
CN-2
Chassis Node
ready
TN-3
Telematics
ready
[00:00]$ShieldVIN verification engine ready.
[00:00]$Select a role and scenario, then press Run.
STEP 1
🔍
Query
Authority sends request + session nonce via VAP-1
STEP 2
🔐
Co-Sign
EN-1, CN-2, TN-3 each sign the nonce in-chip
STEP 3
⚙️
ZK Proof
Proof server generates PLONK/KZG proof from witness data
STEP 4
🌐
Validate
Midnight Network checks proof against VIT token
STEP 5
📤
Disclose
Role-specific fields returned. All others remain private.
Disclosed Fields — Police
🚔
Police / Law Enforcement
Roadside or border check. Needs stolen status, not owner identity.
🛡
—
PLONK proof · Midnight Network · VIT-1
Awaiting verification...
What the ZK proof protects: The private witness data — the three Ed25519 signatures, the actual signing keys, and any private vehicle data — is never submitted to Midnight Network. Only the proof of correct computation is on-chain. The requester cannot reconstruct the witness even if they intercept the proof.
Police Query Explained
A police officer at a roadside stop needs to know one thing: is this vehicle stolen? They do not need the owner's identity or purchase history — and ShieldVIN structurally prevents over-disclosure. Even if the status is Active, the VIN is not disclosed. Only when status is Stolen does the circuit disclose the VIN — to help identify the legitimate vehicle.