Trust graphs for governance,
built to be shared.
Open Trust is the first platform for creating trust graphs intended for multi-app interoperability. A graph's rules are fixed at declaration and published as an EAS attestation — so every app that reads it computes the same answer, and nobody, including us, can quietly change what it means.
Why this exists
Declare your own, or use an existing one
A graph is one attestation naming its roots, its scoring algorithm and who may vouch. Declaring costs a signature. Joining someone else's costs the same, and you never need their permission to read it.
Onchain or offchain EAS attestations
Both venues land in the same index, so the API cannot tell them apart and neither can you. Offchain is free and private; publishing the same vouch onchain later supersedes it rather than replacing it.
Sepolia, Mainnet or Base
Pick where a graph lives when you declare it. The schema UID is identical on every chain, so a graph is not stranded by the choice.Sepolia · liveEthereum · soonBase · soon
Interoperable by construction
The rules live in the attestation, not in our database. Any application can resolve the same declaration, apply the same algorithm and get the same weights — which is what makes a reputation portable instead of captive.
How it works
- 01
Declare
Pick your identity key, root policy, where vouches live, and the scoring algorithm. All of it is frozen into one EAS attestation whose UID becomes the graph's identity.
- 02
Vouch
Vouches are EAS attestations, onchain or offchain. Whichever venue a graph allows, they arrive in the same index — so the API cannot tell them apart, and neither do you.
- 03
Serve
Query weights for one address or thousands, ranked and deterministic. The same snapshot renders as an explorable graph, so a score can always be traced back to the vouches behind it.
Declared so far
All 5 graphs →Where this is going
- 1Iterate on standards & APISo a graph means the same thing to every app that reads it.
- 2Partner with as many organizations as possibleA trust graph with one consumer is a database.
- 3Figure out licensing & governanceOpen questions, stated as open questions.
- 4Improve trust & governance solutions across Web3The reason for the other three.
For builders
Every graph is readable over a REST API with an API key. Scores are precomputed and served from a cache keyed on the graph's state, so a query is a lookup rather than a computation — and identical inputs return byte-identical numbers.
curl -H "Authorization: Bearer $OPEN_TRUST_KEY" \ "https://<host>/api/v1/graphs/<slug>/scores?limit=100"