"DID + Verifiable History": a DID method that is the location-independent sibling of did:webvh. A did:vh identifier is only the method prefix and a self-certifying identifier (SCID) derived from the DID's first log entry, so it contains no domain name or path and is not tied to any place where its log is published. It specialises the VH-Log specification: the DID document's history is a hash-chained, signed log (did.jsonl) with optional pre-rotation of keys, witnesses and watchers. Because the DID names no location, a resolver is handed the log (or a reference to it) rather than fetching it from a well-known URL, and the SCID proves the log is the authentic history wherever it came from. Unlike did:webvh it drops the DID-to-HTTPS transformation, the portability parameter and the implicit #files and #whois services. Currently an early draft by a single editor.
LicenciaThe specification is under the W3C Patent Policy (2004) terms and any sample or reference code in the repository is Apache-2.0, per the repository's licence file, which inherits them from the Decentralized Identity Foundation project charter . https://github.com/swcurran/didvh
Estado de Desarrollo 📝 Borrador
PropietarioNo organization is named; the specification lists a single editor and is developed in a personal GitHub repository
Órgano de GobiernoNone named. Developed in the open by a single editor; related specifications VH-Log and did:webvh are separate projects
País Not stated by the project.
Año de Inicio 2026
StackJSON Lines DID log (did.jsonl) of signed, hash-chained entries; witness proofs in did-witness.json; did:key for witness identifiers; cryptographic agility through versioned parameters
Financiamiento Not stated by the project.
Última Investigación 29 oct 2026
Vista de topología
Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.
Identidad soberana Portabilidad del grafo de confianza
Protocolo de Identidad Atributos
OrígenesMaking self-certifying DIDs with verifiable history usable where there is no web host: peer-to-peer exchange, local files, content-addressed storage, by separating the identifier from the place its log lives
Base de DatosNone: each DID's history is its own JSON Lines log, held by the controller and by whoever else copies it (peers, watchers, a web location, IPNS or a local directory)
Lenguaje de ConsultaNone: the resolver is passed the log (or a source reference), verifies every entry and returns the DID document
Formatos de DatosJSON Lines DID log (did.jsonl) of entries whose state is a W3C DID document; witness proofs in did-witness.json; parameters such as method version, update keys and next-key hashes
Soporte Móvil Not stated by the project.
Soporte WebNot stated by the project; a log may be published at a web location, but the DID itself contains none
Aplicaciones NativasNone: a draft specification
TérminosFree; specification and sample code licences as above
Fondos Not stated by the project.
Basado EnVH-Log; did:webvh (log format, SCID, entry hashes, key authorization, pre-rotation and witnesses are those of VH-Log as used by did:webvh); W3C DID Core; did:key for witnesses
PermisosCryptographic capabilities: only keys authorized in the log can update the DID; anyone can verify
Autenticación e IdentidadSelf-certifying: the DID is the SCID derived from the first log entry; entries are signed by keys the log itself authorizes; every entry's identifier must match the first entry's SCID
Modelo de AlmacenamientoStorage-agnostic: the controller must make the log available through at least one source (peers, watchers, web locations, IPNS, a local directory), and a resolver verifies it the same way whichever way it arrived
InteroperabilidadA W3C DID method in a draft; sibling of did:webvh and meant to coexist with it; the did:scid method defines a did:scid:vh format over the same log, and the spec notes a did:vh, a did:scid:vh and a did:webvh DID can never share a log or a SCID
Portabilidad de DatosComplete by design: the DID never changes, so no portability mechanism is needed, and the same log can be served from any source
Gobernanza y Toma de DecisionesNot described: the specification is a personal draft with no process stated
Madurez del Protocolo / EstandarizaciónEditors Draft v0.1 ("Pre-Draft"); no standards body is named, no implementation or test suite is linked, and it is not in the W3C DID Extensions registry
Estándares de IdentidadW3C DID Core; VH-Log; did:key for witness identifiers
Gestión de ClavesKeys authorized in the log; optional pre-rotation by publishing hashes of the next keys (the spec says controllers should use it); updates signed by an authorized key
Tipos de CredencialesN/A: a DID method; it defines no credential types
Método de VerificaciónA resolver verifies every log entry (entry hash, SCID, authorized-key signatures, pre-rotation and witness proofs where used) and checks that each entry's identifier is did:vh plus the first entry's SCID
Funciones de PrivacidadDescribed in the spec's privacy considerations, covering surveillance and correlation and the right to erasure; the log is append-only, so history cannot be erased
Métodos de AutenticaciónSignatures by keys the log authorizes; witnesses can approve updates before publication
Mecanismo de RevocaciónDeactivation by setting the deactivated parameter or emptying the update keys; the history is kept
Tipos de Agentes SoportadosAny key-controlling entity
Tipos de Billetera/ClienteNone yet: no implementation is linked
Mecanismos de RecuperaciónPre-rotation commitments (optional, recommended) let a controller recover from a compromised active key
Cumplimiento / RegulacionesThe spec has a section on the right to erasure under GDPR Article 17
Protocolos de Intercambio de CredencialesN/A: a DID method; its logs can be exchanged peer-to-peer in the manner of did:peer
Marco de ConfianzaCryptographic: the SCID and the entry hashes bind the log to the identifier; optional witnesses and watchers add third-party checks; no registry or authority
Modelo de CostosFree: no registry or host is required
Resistencia a la CensuraHigh by design: there is no authoritative location, so nobody can block resolution by controlling a host; availability still depends on someone holding a copy of the log
Relaciones
Cómo se conecta esta herramienta con otras herramientas y organizaciones, según relaciones revisadas por el responsable de datos de OpenHaven. Describen cómo se conectan los proyectos, no su calidad.