Sovereign DID Stack
Technical Specification
1. Abstract
This specification defines the Sovereign DID Stack — a five-layer decentralized identity architecture designed to provide cryptographic machine identity verification for Level 5 autonomous systems.
The stack closes 43.3 meters of fatal risk at 120 km/h — the combined identity gap (3.33m), visual gap (6.67m), and signal gap (33.3m) that exists in every Level 5 autonomous machine operating without sovereign identity verification.
With the complete stack active, the fatal risk collapses to 2.67 centimeters.
2. Sovereign Stack Architecture
The stack is composed of four DID methods anchored to a Layer 0 foundation. Each layer answers one question every autonomous machine must answer before acting.
| Layer | DID Method | Question | Gap Closed | Latency |
|---|---|---|---|---|
| 0 | w3cdid.com | What standard? | Foundation | — |
| 1 | did:verifiedcar | Who am I? | 3.33m | <800μs |
| 2 | did:viewonwebsite | Is what I see real? | 6.67m | <1ms |
| 3 | did:verifiedhz | Is the signal real? | 33.3m | <1ms |
| L5 | did:level5 | All confirmed? | 43.3m → 2.67cm | <1ms total |
3. DID Syntax
3.1 did:verifiedcar
The did:verifiedcar method defines the identity root for autonomous machine physical identity verification. The DID method syntax follows W3C DID Core v1.1.
did:verifiedcar:MACHINE_IDENTIFIER Examples: did:verifiedcar:root did:verifiedcar:verifiedcar.com did:verifiedcar:vehicle:VIN17DIGITSTRING
3.2 did:viewonwebsite
did:viewonwebsite:VISUAL_IDENTIFIER Examples: did:viewonwebsite:root did:viewonwebsite:viewonwebsite.com
3.3 did:verifiedhz
did:verifiedhz:SIGNAL_IDENTIFIER Examples: did:verifiedhz:root did:verifiedhz:verifiedhz.com did:verifiedhz:gps:1575.42mhz
3.4 did:level5
did:level5:CERTIFICATION_IDENTIFIER Examples: did:level5:root did:level5:certified:MACHINE_ID
4. DID Operations
4.1 Create
DID documents are created by the sovereign authority at hardcodedlogic.com. Creation requires registration through the sovereign enclave at enclave.hardcodedlogic.com.
{
"@context": ["https://www.w3.org/ns/did/v1"],
"id": "did:verifiedcar:root",
"controller": "did:verifiedcar:verifiedcar.com",
"verificationMethod": [{
"id": "did:verifiedcar:root#key-1",
"type": "Ed25519VerificationKey2020",
"controller": "did:verifiedcar:verifiedcar.com"
}],
"service": [{
"id": "did:verifiedcar:root#resolver",
"type": "SovereignIdentityResolver",
"serviceEndpoint": "https://verifiedcar.com/resolve"
}]
}
4.2 Read (Resolve)
DID documents are resolved via the sovereign resolver at each domain's /.well-known/did.json endpoint.
GET https://verifiedcar.com/.well-known/did.json GET https://viewonwebsite.com/.well-known/did.json GET https://verifiedhz.com/.well-known/did.json GET https://didlevel5.com/.well-known/did.json
4.3 Update
Updates are performed by the sovereign authority only. No third party may update sovereign DID documents.
4.4 Deactivate
Deactivation is reserved for sovereign authority action only. The namespace remains permanently occupied regardless of deactivation status.
5. DID Resolution
The sovereign resolver accepts any DID method in the stack and returns the corresponding DID document.
Resolver endpoint: https://w3cdid.com/resolve Query format: https://w3cdid.com/resolve?did=did:verifiedcar:root https://w3cdid.com/resolve?did=did:verifiedhz:root https://w3cdid.com/resolve?did=did:level5:root
Resolution latency: <1ms via Mojo Enclave at enclave.hardcodedlogic.com.
6. Security Considerations
6.1 Sovereign Enclave
All cryptographic operations are performed inside the sovereign Mojo Enclave at enclave.hardcodedlogic.com. The enclave provides sub-800 microsecond identity verification with no external dependencies.
6.2 DNS Security
All sovereign domains are locked across 23+ independent DNS servers on 6 continents. DNS lock confirmed March 7, 2026. Certificate Transparency logs timestamped across Google, Apple, and Cloudflare.
6.3 Bitcoin Anchor
The sovereign proof is anchored to Bitcoin Block 103 — mined January 12, 2009. This timestamp is cryptographically immutable and cannot be backdated by any entity.
6.4 Prior Art
All DID method namespaces were occupied before any competing implementation existed. The namespace is permanently locked. No alternative did:verifiedcar, did:viewonwebsite, did:verifiedhz, or did:level5 can be registered.
7. Privacy Considerations
The sovereign DID stack operates on machine identity — not human identity. No personally identifiable information is stored or transmitted by the stack.
Machine credentials are issued to the vehicle, drone, robot, or autonomous system — not to the operator or passenger. This separation ensures that sovereign identity verification does not create human surveillance infrastructure.
All DID documents are public and machine-readable. No private data is included in any DID document in the sovereign stack.
8. Prior Art & Infrastructure
8.1 Bitcoin Block 103 Anchor
The sovereign proof is anchored to Bitcoin Block 103, mined January 12, 2009 by an unknown miner (non-Patoshi, non-Hal Finney). The sovereign seal SHA256 hash ties the infrastructure timestamp to this immovable historical reference.
Block: 103 Date: January 12, 2009 Value: 50 BTC (unspent) Patoshi: NO — outside Satoshi range Anchor: enclave.hardcodedlogic.com Status: SOVEREIGN CONFIRMED
8.2 DNS Infrastructure
Domains: w3cdid.com, verifiedcar.com, viewonwebsite.com,
verifiedhz.com, didlevel5.com, hardcodedlogic.com
Servers: 23+ independent DNS servers
Coverage: 6 continents
Locked: March 7, 2026
CT Logs: Google, Apple, Cloudflare — timestamped
8.3 W3C Submission
Repository: w3c/did-extensions PR: #671 Method: did:verifiedcar Filed: March 3, 2026 Reviewers: 14 (including Manu Sporny) Status: Open — Under Review Context: Filed 2 days before W3C DID v1.1 Candidate Recommendation