Skip to content
One encounteroffline ok
Ana's devicefresh anchor
did:key:z6MkhaXg…9vQ2
Ben's devicefresh anchor
did:key:z6MkrJVn…3kLp
Ana → Ben encounter credential, signeded25519
Ben → Ana encounter credential, signeded25519
Key control, freshness and deliberate recognition. Nothing more, and never revoked.

Trust through real encounters

Local-first·DTG credentials·Trust Tasks

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.

Editor's drafts@real-life/trust-protocol 0.18.0Powered byDTG credentialsTrust Tasks
Architecture

Four 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.

Identity

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.

More →

Anna, one seed. From it one identifier toward each context: pair identifiers toward Peter, Frida and Sam, group identifiers toward the Choir group and the Garden group, a persona toward the public. None of them links to another.PPeterGarden groupFFridathe publicSSamChoir grouppair/7f3a…group/c41e…pair/a90d…persona/…pair/2b6c…group/e83f…Annaone seed
Encounter

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.

More →

Trust

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.

More →

Access

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.

More →

A group. Its authority log: Anna founds it, Anna admits Peter, Frida and Sam, the rule becomes that two members admit, Peter and Sam remove Frida, which starts a new key epoch. The same log is on the devices of Anna, Peter and Sam, who hold the key. Frida's device is outside now and holds ciphertext only.Annaholds the keyPeterholds the keyFridaremoved · ciphertext onlySamholds the keyAUTHORITYLOGgenesisby Annaadmit Peter, Frida, Samby Annarule: two admitby Anna, Peterremove Fridaby Peter, Sam · new epoch
Shared space

A shared space for the group's work

Events, places, offers, needs, tasks, people and messages: everything the group holds lives in one encrypted space. The relay in between sees ciphertext only.

End-to-end encryptedAES-256 · epoch keys only on member devices
Complete on every devicefull replica · offline first
Changes mergesigned, causally linked entries · CRDT or log, left open
Former members read nothing newkey rotation · a removal starts a new epoch
  • Event
  • Place
  • Offer
  • Need
  • Task
  • Person
  • Message
  • New
  • Anna
  • Peter
  • Samnot yet in sync
  • Outsideciphertext only
Services

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.

Delivery contractsealed · acknowledged · closed set of states
VTI mediatorany transport
Replication contractsigned, causally linked · key-blind
any substrate
In action

See it run

Two simulators in your browser. Real Ed25519, X25519 and AES-GCM, no installation, nothing leaves your tab.

Interoperability

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.

Trust over IP · DTG WG
Status

Where 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.

8specifications converged
0.18.0library on npm, with provenance
2simulators, in your browser
In productionwot-spec, the previous generation

Start where it suits you

Read the foundations, run the simulators, or install the library and reproduce the vectors.