Novel decentralized identifier architecture — "eXtensible IDentifier" — defined as a unique 32-byte identifier for a subject entity (person, organization, device, or any abstract subject), generated from the SHA-256 hash of an inception key. XIDs resolve to XID Documents — Gordian-Envelope-encoded controller documents that bind the identifier to public keys, permissions, endpoints, and delegation rules — and inherit Envelopes selective elision so the controller document can be tailored per-recipient. The defining architectural insight is that holders, not issuers, control which parts of the controller document are revealed to which counterparties. Intentionally not W3C DID-conformant: XIDs are research/architectural exploration positioned alongside (not within) the W3C DID paradigm. Recently extended with "Edges" (BCR-2026-003) to support web-of-trust attestations between XIDs
Detalle del Estado de DesarrolloResearch / pre-spec — partial reference implementation in bc-xid-rust; "open for community feedback"; Q1 2026 Blockchain Commons report describes XIDs as "one of our largest current projects"
PropietarioBlockchain Commons LLC (not-for-profit benefit corporation founded by Christopher Allen, April 25, 2019; Berkeley, California). Specification author: Wolf McNally, Lead Researcher
Órgano de Gobierno Blockchain Commons LLC (not-for-profit benefit corporation)
PaísUSA (Berkeley, California)
Año de Inicio 2024
StackRust (bc-xid-rust); integrated with bc-envelope, provenance-mark crates
FinanciamientoBlockchain Commons donations and patron sponsorships
OrígenesBlockchain Commons; built on the Gordian Envelope architecture; influenced by but explicitly diverging from W3C DID Core
Base de DatosN/A — controller documents are Envelope artifacts; persistence is implementation concern (registry, web URL, blockchain, peer-shared via Garner)
Lenguaje de ConsultaN/A directly — Envelope's selective-disclosure mechanism via inclusion proofs effectively functions as the query model; recipients receive only the parts of the controller document the holder chooses to reveal
Formatos de DatosCBOR (deterministic via dCBOR); 32-byte identifier tagged with CBOR tag #6.40024; XID Documents as Gordian Envelopes
Soporte MóvilYes — libraries cross-compile to mobile platforms; Envelope tooling on mobile via BCSwiftEnvelope
Autenticación e IdentidadSelf-certifying identifier — the XID is the SHA-256 hash of an inception public key, providing cryptographic proof of origin while allowing keys to be rotated without changing the identifier
Modelo de AlmacenamientoXID Documents resolved via dereferenceVia assertions (HTTPS resolvers, BTCR, IPFS, Hubert dead-drops, etc.); decentralized resolution; holders can publish elided versions to different recipients
InteroperabilidadInspired by but intentionally not conformant to W3C DID Core; standalone architecture leveraging Gordian stack; can encode dereferenceVia URIs to existing W3C DID resolvers as a bridge
Portabilidad de DatosBy design — identifier is portable (hash of inception key, no registry binding); controller document portable via Envelope encoding; selective-disclosure subsets cryptographically verifiable independent of full document
Gobernanza y Toma de DecisionesHolder-controlled — architectural commitment that the identifier holder, not the issuer, controls disclosure; this is fundamentally a different governance model from issuer-mediated SSI flows
Estándares de IdentidadSelf-defined (Blockchain Commons Research papers BCR-2024-010 and BCR-2026-003); not W3C DID Core; not OIDC
Métodos DID SoportadosXIDs are not a DID method; XID Documents can reference other DID-resolvable URIs via dereferenceVia
Gestión de ClavesInception key + rotated keys with permission flags; FROST threshold signing for group XIDs; SSKR recovery shares
Tipos de CredencialesEdges (BCR-2026-003) — signed Envelope-wrapped attestations between XIDs forming a web-of-trust graph; can carry any Envelope-encodable credential format
Método de VerificaciónCryptographic verification via Envelope signatures; controller document elision preserves Merkle digest for proof of original content
Funciones de PrivacidadSelective elision per recipient (Merkle-tree privacy); holder-controlled disclosure rather than issuer-controlled; non-correlation across contexts via tailored documents
Métodos de AutenticaciónPublic-key signatures rooted in XID-document keys; Permits (Envelope encryption) for confidential exchanges
Mecanismo de RevocaciónKey rotation (XID stable across rotations); permission flag updates in controller document; provenance-mark-chained Editions track XID Document versions
Tipos de Billetera/ClienteCLI tooling; reference apps in development; Garner publishing system
Mecanismos de RecuperaciónSSKR-based shard recovery; FROST threshold-based recovery; multi-key inception possible
Cumplimiento / RegulacionesNot yet evaluated — XID is a research note (BCR-2024-010) rather than a standardized identity protocol; architectural design supports privacy-by-design and data-minimization principles compatible with GDPR
Protocolos de Intercambio de CredencialesEnvelope-native — assertions exchanged as Envelope artifacts; could be carried over DIDComm or other credential exchange protocols if wrapped in those formats
Marco de ConfianzaSelf-sovereign — no central authority; web-of-trust via Edges (BCR-2026-003); Permits for context-specific trust
Modelo de CostosNo cost (self-generated); resolution costs depend on chosen dereferenceVia method
Resistencia a la CensuraHigh — autonomous identifier generation, decentralized resolution options including Hubert dead-drops on BitTorrent/IPFS
¿Ve algo que falta o que podría mejorarse? Cuéntenos →