Back to How It Works

Vehicle Passport

Tesla Model 3 example

This example demonstrates how a vehicle is tracked through the Passport system. We follow a Tesla Model 3 from factory production through service events, annual inspection, a minor incident, and ultimately a custody transfer.

VIN Privacy

Note that the actual VIN is never stored directly. Instead, we store a hash of the VIN for verification purposes without exposing the full identifier.

Step 1: Passport Created

The vehicle receives a unique passport ID when registered in the system.

Passport Record
json
{
  "passportId": "psp_car_vin_2025_001",
  "assetType": "vehicle",
  "status": "active",
  "mintedAt": "2024-06-01T08:00:00Z"
}

Step 2: Attributes Bound

Core vehicle attributes including VIN hash, make, model, and specifications.

Make

Tesla

Model

Model 3

Year

2024

Color

Midnight Silver

Battery

82 kWh

VIN Hash

sha256:5a4b3c2d1e...

Bound Attributes
json
{
  "vinHash": "sha256:5a4b3c2d1e...",
  "make": "Tesla",
  "model": "Model 3",
  "year": 2024,
  "color": "Midnight Silver",
  "batteryCapacity": "82 kWh"
}

Event Timeline

The vehicle's complete service history, inspections, incidents, and transfers are recorded as append-only events.

provenance

6/1/2024, 8:01:00 AM

evt_001
  • Factory: tesla_fremont_001
  • Production Date: 2024-05-28
  • Initial Mileage: 12 mi
Raw Event Data
json
{
  "eventId": "evt_001",
  "eventType": "provenance",
  "timestamp": "2024-06-01T08:01:00Z",
  "data": {
    "factoryRef": "tesla_fremont_001",
    "productionDate": "2024-05-28",
    "initialMileage": 12
  }
}

service

12/15/2024, 10:00:00 AM

evt_002
  • Service Type: scheduled maintenance
  • Mileage: 12,450 mi
  • Service Center: service_node_tesla_sf
  • Notes: Tire rotation, brake inspection
Raw Event Data
json
{
  "eventId": "evt_002",
  "eventType": "service",
  "timestamp": "2024-12-15T10:00:00Z",
  "data": {
    "serviceType": "scheduled_maintenance",
    "mileage": 12450,
    "serviceCenter": "service_node_tesla_sf",
    "notes": "Tire rotation, brake inspection"
  }
}

verification

1/10/2025, 2:00:00 PM

evt_003
Inspection PassedVerifier Node
  • Type: annual safety
  • Result: pass
  • Mileage: 15,230 mi
Raw Event Data
json
{
  "eventId": "evt_003",
  "eventType": "verification",
  "timestamp": "2025-01-10T14:00:00Z",
  "verifier": {
    "nodeId": "verifier_inspection_ca",
    "type": "verifier_node"
  },
  "attestation": {
    "verified": true,
    "inspectionType": "annual_safety",
    "result": "pass",
    "mileage": 15230
  }
}

incidentaccident_history

1/18/2025, 4:30:00 PM

evt_004
Incident Recorded
  • Type: minor collision
  • Severity: low
  • Repaired: Yes
  • Insurance Ref: claim_ref_hidden
Raw Event Data
json
{
  "eventId": "evt_004",
  "eventType": "incident",
  "timestamp": "2025-01-18T16:30:00Z",
  "data": {
    "type": "minor_collision",
    "severity": "low",
    "repaired": true,
    "insuranceRef": "claim_ref_hidden"
  },
  "flag": "accident_history"
}

custody transfer

1/21/2025, 9:00:00 AM

evt_005
From:

owner_custody_001

To:

buyer_custody_002

Private sale completed

Raw Event Data
json
{
  "eventId": "evt_005",
  "eventType": "custody_transfer",
  "timestamp": "2025-01-21T09:00:00Z",
  "from": {
    "nodeRef": "owner_custody_001"
  },
  "to": {
    "nodeRef": "buyer_custody_002"
  },
  "notes": "Private sale completed"
}

Key Observations

Mileage Tracking

Each service and inspection event records the current mileage, creating a verifiable odometer history that cannot be tampered with.

Incident Transparency

The accident flag is permanently recorded but shows the incident was minor and repaired. This provides transparency without hiding history.

Privacy by Design

No personal information appears in this passport. The VIN is hashed. Insurance references are opaque. Custody transfers use node references only. A buyer can verify the vehicle's history without learning anything about previous owners.
Built with v0