Verifiable trust
Proof you can check yourself.
A Vin2 certificate isn't a claim you have to take on faith. It's a W3C Verifiable Credential — a standards-based document a buyer, an auction house, or an insurer can verify independently, offline, without trusting Vin2. Four things are proven, and you can check each one.
Identity
Each vehicle gets one deterministic Vin2 ID + DID, minted from its VIN. The record stays bound to the car.
Decentralized Identifier (did:key)
Integrity
The record's hash is committed to an append-only Merkle ledger. Change one field and the proof breaks.
Merkle tree + SHA-256
Signature
Vin2 signs the record with an Ed25519 key. Anyone checks the signature against the published public key.
Data Integrity, eddsa-jcs-2022
Status
A credential can be revoked without re-issuing it — and you can confirm it hasn't been.
W3C Bitstring Status List
Open standards, no proprietary glue
Why "you don't have to trust us" is literally true.
The certificate is built entirely on published, current standards. The issuer key travels in the credential itself, so verification needs no call back to Vin2 — any compliant verifier works.
W3C Verifiable Credentials 2.0W3C Data Integrity — eddsa-jcs-2022Ed25519 (RFC 8032) signaturesDecentralized Identifiers (did:key)W3C Bitstring Status ListJSON Canonicalization Scheme (RFC 8785)
Check one for yourself.
Resolve a VIN, verify a certificate's inclusion + signature, or paste a full credential.