Questions

A signed public statement about someone, recorded on-chain through the Ethereum Attestation Service. A vouch is one kind. You can revoke it later.

Your community does, when the network is created. They anchor the whole graph, so choosing them well is the real work. On a controller-backed network, Settings can draft and preview a later change, then routes the complete configuration through the controller’s actual owner — a wallet, Safe, or operational timelock. The next checkpoint activates it; settled rounds do not change.

In rounds. Each round freezes the set of vouches at a cut-off, someone proves the new scores, and the result goes on-chain. Every network sets its own pace, and a settled round is never recalculated.

Not with money. Buying score means getting genuinely trusted people to vouch for you. What no algorithm stops is a trusted person vouching badly, which is a problem every community already has.

Score comes from trust flowing out of the starting accounts. A thousand bots vouching for each other form an island with lots of arrows and nothing flowing in, so none of those vouches earns any trust. The create form reserves the full starting share by default, which leaves a disconnected island at zero. A community can lower that advanced setting, but then every other account gets an equal slice of the remainder and a big enough island can hold a real share.

No. Vouches, rules, code, and scores are all public. That is what makes the scoreboard checkable by anyone.

Nothing. It isn’t there for privacy. It’s there so a whole scoreboard can be verified in one cheap on-chain check instead of everyone recomputing millions of scores.

The chain keeps a running commitment to every attestation as it lands. A proof only verifies if it consumed exactly that set, so a prover can’t quietly drop the vouches they dislike or add ones that never happened.

Anyone. It takes one transaction and nobody approves it.

Proving costs real money, so each network has a tank to pay whoever produces its scoreboard, once someone sets its per-round limit. Networks we curate will be proven at our expense. Pricing for everyone else is still being worked out.

Only if nobody else proves your rounds. Proving is permissionless, so anyone can freeze a round and land the result, and no operator can lock you out. Today that mostly means you or us: a tank cannot pay a bounty until someone sets its per-round limit with a direct contract call, and the networks we curate will be proven at our expense. If every machine we run vanished, anyone could recompute the scores of a network created through the app from what is on the chain, and prove them.

Yes. A vouching network’s scoreboard downloads as CSV or JSON, and any contract can check one account’s score against the on-chain root, given the score and its proof.

Trustgraphs is still pre-production. Review the contracts, program semantics, deployment configuration, source availability, and governance assumptions before using an output for a decision with material consequences.

Not by an outside firm. Point a network at something you can afford to get wrong.

The code and the design docs are open. Start with the plain-language explainer, then the algorithm spec.