did:verifiedcar DID Method Specification

Abstract

The did:verifiedcar DID method defines a domain-anchored Decentralized Identifier system optimized for Level 5 autonomous vehicle authentication. It achieves sub-1ms local identity establishment — completing the full authentication handshake in under 800 microseconds — entirely before V2X transport begins.

This separation of authentication from transport (Auth ≠ Transport) is the core architectural contribution. At 120 km/h, a standard 100ms authentication handshake creates 3.3 meters of uncontrolled vehicle travel. The did:verifiedcar method reduces this to 2.67 cm — within Level 5 orchestration tolerance.

1. Introduction

Decentralized Identifiers (DIDs) as defined by the W3C DID Core specification provide a foundation for verifiable, self-sovereign identity. The did:verifiedcar method extends this foundation to address the physical safety requirements of Level 5 autonomous vehicle coordination.

Existing DID methods assume network-dependent resolution, introducing latency incompatible with real-time vehicular safety systems. The did:verifiedcar method resolves identity locally — without DNS, without network round-trips — establishing sovereign vehicle identity before any data transmission occurs.

2. The did:verifiedcar Format

2.1 Method Name

The method name is: verifiedcar

2.2 DID Syntax

did:verifiedcar:<vehicle-identifier>

Examples:
  did:verifiedcar:v1-0x4A2F-dubai-001
  did:verifiedcar:enclave-node-AE-001
  did:verifiedcar:root

2.3 Identifier Components

3. Architecture — Auth ≠ Transport

3.1 Layer Separation Principle

The fundamental architectural principle of did:verifiedcar is the strict separation of authentication from transport. Just as TLS session establishment does not equal TCP propagation delay, the Mojo Enclave handshake does not equal V2X radio propagation.

LAYER 4 — V2X TRANSPORT         DSRC / C-V2X / 5G-NR     500μs–10ms
LAYER 3 — TOKEN CARRIER         Signed Identity Token     <10μs
LAYER 2 — ORCHESTRATION         Level 5 Coordination      <100μs
LAYER 1 — HANDSHAKE AUTH        Mojo Enclave              <800μs  ← HERE

3.2 Authentication Sequence

1. Step 1 — Enclave Activation (~0ns): Vehicle CPU loads hardcoded root constants from register. verifiedcar.com identity confirmed at compile-time BUS coordinate.
2. Step 2 — Static Map Resolution (2–11ns): O(1) lookup via ROM_LUT_0x4A2F. No DNS. No network. Direct bus coordinate access.
3. Step 3 — GC-Free Auth Execution (~370ns): ASAP deallocation. Zero pause. SIMD parallel verification of root key pair.
4. Step 4 — SIMD Cryptographic Sign (<500μs): ECDSA signature generated using hardware AES-NI. Identity token sealed in register.
5. Step 5 — Handshake Complete (<800μs): Sovereign identity token sealed. Level 5 authority established.
6. Step 6 — V2X Transport (begins after Step 5): Token carried via DSRC / C-V2X / 5G-NR. Network propagation adds 500μs–10ms. Identity was already established.

4. DID Document Format

{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://verifiedcar.com/ns/did/v1"
  ],
  "id": "did:verifiedcar:v1-0x4A2F-dubai-001",
  "controller": "did:verifiedcar:root",
  "verificationMethod": [
    {
      "id": "did:verifiedcar:v1-0x4A2F-dubai-001#auth-key-1",
      "type": "EcdsaSecp256k1VerificationKey2019",
      "controller": "did:verifiedcar:v1-0x4A2F-dubai-001",
      "publicKeyHex": "<ECDSA public key>"
    }
  ],
  "authentication": [
    "did:verifiedcar:v1-0x4A2F-dubai-001#auth-key-1"
  ],
  "service": [
    {
      "id": "did:verifiedcar:v1-0x4A2F-dubai-001#v2x-endpoint",
      "type": "V2XAuthenticationService",
      "serviceEndpoint": "https://verifiedcar.com/resolve"
    }
  ],
  "hardcodedLogic": {
    "enclaveVersion": "1.0.0",
    "handshakeLatency": "<800μs",
    "lookupTable": "ROM_LUT_0x4A2F",
    "safetyMargin": "2.67cm @ 120km/h"
  }
}

5. CRUD Operations

5.1 Create

A did:verifiedcar DID is created by registering a vehicle identity with the Mojo Enclave. The enclave generates an ECDSA key pair and anchors the public key to verifiedcar.com as root of trust.

5.2 Read (Resolve)

Resolution is performed locally via ROM_LUT_0x4A2F — O(1) lookup with no DNS dependency. For external verification, the resolver at https://verifiedcar.com/resolve/{did} returns the full DID document.

5.3 Update

DID documents may be updated by the controlling enclave. Updates are signed with the existing ECDSA key and timestamped. The root of trust at verifiedcar.com maintains version history.

5.4 Deactivate

Deactivation is performed by the Sovereign Architect via authority@hardcodedlogic.com. A deactivated DID returns a tombstone document with the deactivation timestamp.

6. Security Considerations

• Root of Trust: verifiedcar.com is registered under a 10-year continuous time-lock via ICANN, preventing third-party alteration or seizure.
• Key Security: Private keys are hardware-isolated within the Mojo Enclave. Keys never leave the enclave in plaintext.
• Replay Protection: Each identity token includes a timestamp and nonce, preventing replay attacks.
• No DNS Dependency: Local resolution via ROM_LUT_0x4A2F eliminates DNS spoofing and man-in-the-middle risks during authentication.

7. Privacy Considerations

• Vehicle identifiers are pseudonymous by default.
• No personally identifiable information is included in the DID document.
• Resolution logs are not retained beyond the active session.

8. Physical Safety Proof

9. Reference Implementation

A reference resolver implementation is available at:

• GitHub: https://github.com/hardcodedlogic/did-verifiedcar
• Live Resolver: https://verifiedcar.com/resolve
• DID Configuration: https://verifiedcar.com/.well-known/did-configuration.json

10. Conformance

This specification conforms to the W3C Decentralized Identifiers (DIDs) v1.0 specification published at https://www.w3.org/TR/did-core/.

Sovereign Architect: Tamer Maher Eldebes
Organization: Hardcoded Logic — Sovereign Infrastructure
Domain: hardcodedlogic.com | verifiedcar.com
Contact: authority@hardcodedlogic.com
Date: February 2026
From Dubai with Love, and from Google with Logic.