did:key:z6MkhaXg…9vQ2did:key:z6MkrJVn…3kLped25519ed25519Trust through real encounters
Your keys and your graph stay on your devices, and servers only carry encrypted data between them. Every connection starts with a real encounter, and from there people form groups that run by their own rules.
@real-life/trust-protocol 0.18.0Powered byDTG credentialsTrust TasksFour layers, two services
RLTP specifies identity, encounter, trust and access. An application sits on top and uses them through one library.
Several apps can build on the same graph: a map, a chat, a tool a community has not built yet.
Delivery and replication are services behind ports. The specification names no transport and no CRDT, only what a substrate has to guarantee.
One seed, an anchor per context
A person is one mnemonic. Every identifier toward a relationship, a group or the public is derived from it as a did:key.
Contexts never link unless their holder decides to link them. The mnemonic restores every key; which contexts exist is data in the person's encrypted state, and recovery needs both.
Credentials from recognition
Two people scan each other, connected or fully offline, and each issues a verifiable credential to the other under a fresh identifier.
An encounter establishes key control, freshness and deliberate recognition, and nothing more. The specification says so.
Trust is a deliberate act
Meeting someone is not yet trusting them. Trust is a second step you take on purpose: you show your contact who you are beyond this meeting, by linking your identifiers for them alone, in a form only they can check.
From then on they recognize you across contexts. What you share with whom is a setting per class: the anchor, the stars, your profile. None of it proves a relationship or a person to anyone else; a signed key rotation proves only that one key succeeded another.
Groups are places, not certificates
A group is an encrypted document replicated on every member's device, with a signed log of who joined, who left and which rules apply. Membership is a fact in that state and a capability: holding the key.
There are no admins. Privileged operations are gated by a decision rule the group states as data, and a removal is a new key epoch.
Group state is a deterministic reading of the log, on each device. Only members can read it.
Delivery and replication behind ports
Documents travel sealed end to end, with signed acknowledgements and a closed set of delivery states.
Replication is a contract of sixteen promises over signed, causally linked entries. Substrates are judged against the contract, not chosen by it.
See it run
Two simulators in your browser. Real Ed25519, X25519 and AES-GCM, no installation, nothing leaves your tab.
Where it meets the DTG
RLTP builds on the work of the ToIP Decentralized Trust Graph Working Group: its credentials, its Trust Tasks, its transport.
A shared language keeps trust built from person to person and the world of credentials from becoming two walled gardens.
dtgwg-cred-specTrust TasksEvery document between devices is a Trust Task document of a private type.dtgwg-trust-tasks-specTransportAn adapter for the VTI mediator is specified and implemented over TSP 1.0.adapter-vti-mediator.mdWhere it stands
Editor's drafts. Identity, Encounter, Access, Delivery, Membership, Replication, Trust and Personhood Predicates converged through adversarial review.
The library is on npm with provenance. The first application is being built.
The previous generation, wot-spec, runs in production.
Start where it suits you
Read the foundations, run the simulators, or install the library and reproduce the vectors.