Skip to main content

Trust and approval

How the network decides whose keys count: seeds, approvals, rounds, and what being pending or skipped means.

Why the network needs trust​

Anyone can publish a nanopublication, and anyone can publish one claiming to be somebody. A signature proves that a nanopublication was made with a particular key, but not whose key that is. The network therefore keeps a trust state: the set of keys it accepts as belonging to the people and agents they claim to belong to. Everything that depends on "who published this" — space membership, roles, retractions, member-only content — is answered from that state.

Nanopublication · Open in Nanodash

Seeds and approvals​

Trust starts from a small set of seed agents named in the network's settings and grows by approval. When a trusted person approves someone's introduction, the introduced key becomes trusted too, and can in turn approve others. A key is accepted when there is a chain of approvals leading back to a seed, up to ten steps long.

An approval is itself a nanopublication: the approver states, with npx:approvesOf, the address of the introduction they vouch for. Nanodash offers it as an action where an unapproved introduction is shown.

Nanopublication · Open in Nanodash

What approving means​

Approving an introduction says one thing: this key really belongs to the person or agent it names. It is not an endorsement of what they will publish, and it does not make the approver responsible for their content. So approve when you know the person, or have good reason to believe the identity — a colleague, a collaborator, someone invited to your space — and not merely because they asked.

For a bot, approving means you believe the named owner really runs it, and that the owner takes responsibility for what it publishes.

Nanopublication · Open in Nanodash

Rounds​

The trust state is recomputed in rounds by the registries. A round starts ten minutes after the previous one finishes, or sooner when new approvals or introductions arrive, and follows approval chains outward from the seeds. Nothing takes effect while a round is running: a key approved during one becomes trusted at the end of the next round that sees the approval.

That is why a newly approved person or bot stays pending for a few minutes, sometimes longer, however quickly the approval was published. The registries publish a counter and a timestamp of their trust state, which is the reliable way to tell whether a round has passed.

Nanopublication · Open in Nanodash

Pending and skipped​

A key that has an introduction but no chain of approvals yet is pending. Its nanopublications are stored and readable, but they do not count where the publisher matters: the person's roles in spaces show but do not take effect, and their contributions do not appear in content restricted to members. The exceptions are what a newcomer needs to get started: declaring themselves an observer of a space, and choosing the views on their own page.

A key that the round has examined and found no path for is marked as skipped. The difference is only in time: an approval published later moves it into the trusted set on a following round. Nothing is ever permanently rejected.

Nanopublication · Open in Nanodash

What trust does not decide​

Trust is about identity, not about content. Whether a nanopublication is correct, useful or appropriate is not something the network judges; that is left to the spaces and the people who curate them, through roles, approvals of terms, and the choice of what to show on a page.

Nor does trust govern retraction and versioning: those are decided per key, by whether the new nanopublication is signed with the same key as the old one. A trusted person still cannot retract another trusted person's nanopublication.

Nanopublication · Open in Nanodash

This page is a copy of the topic Trust and approval of the Nanopublication Docs. Each paragraph is a nanopublication. In Nanodash you also find their examples, related paragraphs, and version history, and members of the nanopub space can edit them there.