did:webvh

Protocolo de Identidad

A W3C DID method that extends did:web with cryptographically verifiable history, self-certifying identifiers (SCIDs), and key pre-rotation. Every DID version is cryptographically chained to its predecessor through a signed DID log; updates require signatures from authorized keys. A did:webvh URL is backwards-compatible with did:web (resolve in "legacy mode" by dropping the "vh" and SCID segment) while providing enhanced trust guarantees when resolved natively. Incubated at DIF Identifiers & Discovery Working Group; v1.0 released 2025 with three complete implementations.

Comunidad
Enlaces
Visitar Comunidad

Detalles

Licencia Permissive (Apache-2.0); https://github.com/decentralized-identity/didwebvh — specification; https://github.com/decentralized-identity/didwebvh-ts — TypeScript; https://github.com/decentralized-identity/didwebvh-server-py — Python; Rust implementation donated by Affinidi
Estado de Desarrollo 🟢 Activo
Detalle del Estado de Desarrollo Released (v1.0 specification at identity.foundation/didwebvh; three complete implementations: TypeScript (didwebvh-ts), Python (didwebvh-server-py), Rust (donated by Affinidi); Dockerized installation option; deployed in Swiss swiyu national trust infrastructure)
Propietario Decentralized Identity Foundation (DIF) — Identifiers & Discovery Working Group; specification co-created by Stephen Curran (BC Government) and John Jordan; originally incubated as did:tdw (Trust DID Web) at BC Government
Órgano de Gobierno DIF (Identifiers & Discovery Working Group)
País International (DIF is globally distributed; incubated by Government of British Columbia, Canada; now DIF-governed)
Año de Inicio 2023
Stack Language-agnostic specification; implementations in TypeScript (Bun/Node.js), Python (FastAPI), Rust; HTTPS for DID document hosting; JSON-LD for DID documents
Financiamiento Foundation / Government (DIF member funding; original incubation by Government of British Columbia; ongoing development by DIF I&D Working Group contributors)
Última Investigación 1 jul 2026

Dominios de Caso de Uso

Identidad y Confianza

Protocolo de Identidad Atributos

Orígenes DID ecosystem / enterprise identity (motivated by did:web's lack of verifiable history and self-certification; designed as a "grown-up" production-grade upgrade to did:web with cryptographic provenance and key rotation without ledger dependency)
Base de Datos N/A (DID log stored as append-only file at well-known HTTPS URL; no database required by spec)
Lenguaje de Consulta DID URL resolution (standard W3C DID resolution via HTTPS; DID log fetched and verified client-side)
Formatos de Datos W3C DID Document (JSON-LD); DID Log (append-only JSON Lines file of signed DID document versions); data integrity proofs per version
Soporte Móvil Library-level (TypeScript and other SDKs usable in mobile environments; no dedicated mobile app)
Soporte Web Yes (HTTPS-based DID document hosting; standard web infrastructure)
Aplicaciones Nativas Library-level (embedded in DID resolver libraries and server implementations; no standalone app)
Términos Free / Open standard (Apache-2.0; no fees)
Fondos Unknown (DIF member contributions; BC Government R&D investment not separately disclosed)
Basado En W3C DID Core specification; did:web (backwards-compatible upgrade); SCID (self-certifying identifier derived from genesis state); data integrity proofs; JSON Lines log format
Permisos Cryptographic Capabilities (key control determines update permissions; multi-key authorization possible; no ACL)
Autenticación e Identidad Self-certifying DID (SCID derived from initial DID document state; full cryptographic key history verifiable from log; backwards-compatible did:web resolution)
Modelo de Almacenamiento Web-hosted (DID log stored at well-known URL alongside DID document; standard HTTPS hosting; no blockchain or distributed ledger required)
Interoperabilidad W3C DID ecosystem (any DID consumer); backwards-compatible with did:web (legacy mode resolution); Swiss swiyu national trust infrastructure deployment; Hyperledger ACA-py integration
Portabilidad de Datos Full portability (DID can be moved to new HTTPS host via portability mechanism; SCID and history preserved; key rotation supported without identity loss)
Gobernanza y Toma de Decisiones Foundation-governed (DIF Identifiers & Discovery Working Group; DIF membership governance)
Madurez del Protocolo / Estandarización Community Standard (v1.0 released 2025; three complete implementations; DIF Identifiers & Discovery Working Group; deployed in Swiss national infrastructure; Apache-2.0; not yet submitted to W3C DID Methods Registry as a formal W3C standard)
Estándares de Identidad W3C DID Core 1.0; W3C Data Integrity; SCID (Self-Certifying Identifier); compatible with W3C Verifiable Credentials
Métodos DID Soportados did:webvh (defines this method); backwards-compatible with did:web
Gestión de Claves User-controlled with pre-rotation (authorized keys listed in DID log; key rotation recorded as new signed log entry; pre-rotation commitments supported for forward security)
Tipos de Credenciales N/A (DID method specification; compatible with any W3C VC issued against did:webvh identifiers)
Método de Verificación Cryptographic signature verification (each DID log entry carries data integrity proof signed by authorized key; full history verifiable from SCID genesis; no external trust anchor required)
Funciones de Privacidad Minimal (web-hosted DID is publicly discoverable; SCID enables portable history without exposing private keys; no ZKP features in base spec)
Métodos de Autenticación Cryptographic signatures (DID-based key control; standard DID authentication challenge-response)
Mecanismo de Revocación Key rotation via DID log (new log entry with updated keys signed by currently authorized key; revoked keys removed from active verification methods; history preserved immutably)
Tipos de Agentes Soportados Humans (individuals), Organizations, Services/APIs, Devices/IoT — any entity with HTTPS hosting capability
Tipos de Billetera/Cliente SDK/Library integration (TypeScript, Python, Rust libraries); server-side implementations; compatible with standard W3C DID wallets and agents
Mecanismos de Recuperación Pre-rotation / Key history (recovery via pre-committed rotation keys; M-of-N multisignature possible via DID document configuration)
Cumplimiento / Regulaciones eIDAS-aligned (Swiss swiyu national trust infrastructure deployed did:webvh for eIDAS-compatible national identity; GDPR-compatible via standard HTTPS infrastructure)
Protocolos de Intercambio de Credenciales Compatible with DIDComm, OIDC4VC, ACA-py / Hyperledger Aries; any protocol supporting W3C DID resolution
Marco de Confianza Cryptographic verification (no external trust anchor required beyond HTTPS; optional governance layer via trust registries for ecosystem deployments)
Modelo de Costos Free (no blockchain fees; standard HTTPS hosting costs; open source libraries)
Resistencia a la Censura Service provider dependent (relies on HTTPS hosting; DID owner controls the hosting; portability mechanism allows migration if host becomes unavailable; not as censorship-resistant as blockchain-anchored methods)