Real Life Trust Protocol (RLTP)

Protocolo de Identidad

A family of specifications, schemas and test vectors for a decentralized trust protocol rooted in encounters between people, published by the Real Life Organisation. It is layered: identity (a key-derived anchor per person and pairwise anchors), encounter (a ceremony in which two people confirm they met), trust, and access (groups as places, with policy and epochs), with delivery and replication kept behind ports. It follows the Decentralized Trust Graph work at Trust Over IP, binds Trust Spanning Protocol through a mediator adapter, and is the third generation of a protocol whose second generation runs in the Web of Trust app. Every document is an Editor's Draft .

Comunidad

Detalles

Licencia Specification text and vocabulary: CC BY 4.0. Library, schemas, contexts, test vectors, conformance suite, simulators and scripts: Apache-2.0. The second-generation Web of Trust app and Real Life Stack: MIT
Estado de Desarrollo 📝 Borrador
Detalle del Estado de Desarrollo Draft (all specifications are Editor's Drafts, for example Identity 0.55 and Encounter 0.32; a reference library, conformance runner and browser simulators exist; the third-generation app is in preparation and the project says an independent implementation is 'the goal, not yet a fact')
Propietario The Real Life Organisation (real-life.org); no legal form or seat is stated on the pages read
Órgano de Gobierno None stated; specifications are reviewed in rounds by independent reviewers and feedback goes through the repository's issues
País Not stated by the project.
Año de Inicio 2026
Stack JavaScript reference library (published to npm) and Node reference engine; JSON Schemas, a pinned JSON-LD context, deterministic test vectors and a conformance runner; Ed25519 and X25519 keys derived from a BIP-39 mnemonic with HKDF-SHA-256; JCS canonicalization (RFC 8785); browser simulators
Financiamiento Not stated by the project.
Última Investigación 12 nov 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.

Vista de topología: Real Life Trust Protocol (RLTP)Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.Real LifeTrust Proto…DIDs (Cumple con)DIDsVCs (Cumple con)VCsdid:key (Se identifica mediante)did:keyTrust Spanning Protocol (Habla el protocolo)TrustSpanning Pro…

Abrir en el Explorador de grafo

Capacidades

Identidad soberana Atestaciones portátiles Portabilidad del grafo de confianza Grupos combinables

Protocolo de Identidad Atributos

Orígenes The third generation of a protocol for building trust from in-person encounters; the second generation (wot-spec) runs in the Web of Trust app, and its users are to move to the third generation once their identities are migrated
Base de Datos N/A: a specification; it names no transport and no CRDT, and defines replication and delivery as contracts behind ports
Lenguaje de Consulta N/A
Formatos de Datos JSON documents with JSON Schemas and a pinned JSON-LD context; W3C Verifiable Credentials 2.0 with a Decentralized Trust Graph RelationshipCredential structure and Data Integrity proofs (eddsa-jcs-2022); JCS canonicalization
Soporte Móvil Not stated by the project; the third-generation app is in preparation
Soporte Web Browser simulators are published; a web app (Web of Trust) implements the second generation
Aplicaciones Nativas Not stated by the project.
Términos Free: CC BY 4.0 specification text and Apache-2.0 code
Fondos Not stated by the project.
Basado En W3C DID Core and Verifiable Credentials 2.0, the Decentralized Trust Graph credentials work at Trust Over IP, DIDComm and Trust Spanning Protocol (through a delivery adapter), and the project's own earlier generations
Permisos Open: CC BY 4.0 specification text; Apache-2.0 code
Autenticación e Identidad A did:key anchor derived from a BIP-39 recovery phrase, with pairwise anchors per relationship and a fresh challenge-based encounter ceremony in which both parties confirm
Modelo de Almacenamiento Keys are restored from the recovery phrase, but state needs an encrypted copy at a storage service whose contract is still unwritten; otherwise a person starts anew
Interoperabilidad Medium: aligns with Decentralized Trust Graph ceremonies and Trust Tasks; binds Trust Spanning Protocol through a mediator adapter that runs live; a replication contract maps p2panda, Keyhive, SECSYNC, NextGraph and Automerge (the mapping was not read)
Portabilidad de Datos Keys are portable through the recovery phrase; state portability depends on the storage-service contract that is not yet written
Gobernanza y Toma de Decisiones Editor-led: each draft is reviewed in rounds by an independent adversarial reviewer, every finding is triaged and answered, and a layer counts as converged when consecutive rounds produce no blocker-level findings
Madurez del Protocolo / Estandarización Editor's Drafts (Identity 0.55.0-draft, Encounter 0.32.0-draft, dated 2026-10-27; Access 0.58, Delivery Contract 0.85); aligned with, but not submitted to, a standards body
Estándares de Identidad W3C Verifiable Credentials 2.0; Decentralized Trust Graph credentials (Working Draft 0.6.0); did:key; Ed25519 (RFC 8032), X25519, HKDF, JCS (RFC 8785), BIP-39
Métodos DID Soportados did:key only (the anchor); did:key identifiers cannot rotate, so the community anchor rotates through generations with a pre-committed next key; did:peer:2 appears only in an informative interoperability check
Métodos DID Soportados - Lista
Gestión de Claves Keys derived from a 12 or 24-word BIP-39 phrase with HKDF-SHA-256 for Ed25519 signing and X25519 agreement; pre-rotation binding of the next anchor key; recovery must not require a custodian of key material
Tipos de Credenciales Encounter credentials and cards (immutable), relationship credentials in the Decentralized Trust Graph form, trust and personhood predicates (draft)
Método de Verificación Data Integrity proofs (eddsa-jcs-2022) over JCS-canonicalized JSON with SHA-256; challenge-response in the encounter ceremony
Funciones de Privacidad Pairwise anchors aim for unlinkability, which the identity specification says holds until disclosed or stolen; storage services see sealed envelopes, sizes and timing
Métodos de Autenticación An in-person encounter ceremony with a fresh single-use challenge per enactment, confirmed by both parties; a fresh pair anchor per enactment
Mecanismo de Revocación Device revocation per group in the access layer; encounter credentials are immutable and not revocable; revocation of the person's anchor is not stated
Tipos de Agentes Soportados People and their devices; groups as places; delivery services and mediators
Tipos de Billetera/Cliente The second-generation Web of Trust app (production); a third-generation app is in preparation; browser simulators
Mecanismos de Recuperación The recovery phrase restores keys, not state; losing the phrase is cryptographically final; restoring state needs an encrypted copy at a storage service
Cumplimiento / Regulaciones None claimed: the encounter specification states that the protocol does not prove personhood; GDPR and eIDAS are not stated in the layers read
Protocolos de Intercambio de Credenciales Delivery through contracts behind ports; the first adapter binds Trust Spanning Protocol through the VTI mediator; Trust Tasks follow the Decentralized Trust Graph framework
Protocolos de Intercambio de Credenciales - Lista
Marco de Confianza Trust grows from verified in-person encounters recorded as credentials, then a trust layer and personhood predicates (drafts); no accredited trust framework is stated
Modelo de Costos Free specification and open-source code; no commercial terms stated
Resistencia a la Censura Not stated by the project; the specification names no transport and relies on delivery adapters

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.

Cumple con
Habla el protocolo
Se identifica mediante