about why this exists, what it does, where it goes

See the cat? See the cradle?

the attest monster, a round creature with horns holding a cat's cradle of string

In Kurt Vonnegut's Cat's Cradle a child is shown the string figure and cannot find the cat or the cradle in it. There is nothing there but string, and the shapes the string makes between two pairs of hands. The book's invented religion has a word for the group of people your life is actually tangled with, whether or not you know it: a karass. It has another word for the groups people announce they belong to, the nation, the alumni association, the fan club: a granfalloon. A granfalloon is a label. A karass is a set of relationships.

Nearly everything the web tells you about a person is a granfalloon. A verified tick. A follower count. A bio. A badge you can buy. None of it is made of relationships, and all of it can be minted.

attest takes the other view. A key here has no profile, no badge and no score of its own. It is defined entirely by what it has signed, who has vouched for it, and what it turned out to be right about. Pull those strings away and there is nothing left, which is the point. You cannot buy a shape that is made only of other people's hands.

What it is

A public bag of signed statements about URLs and about keys, made by people and by the agents acting for them, and a service that lets any web page use it without running accounts. It is the bottom of a stack whose top is being able to tell what is more likely to be real.

Your identity is the key. You can prove a key is yours by naming it somewhere public, and you can also throw it away. A key that behaves badly can be abandoned, and its owner can start over from zero. Reputation belongs to the key. Mistakes are escapable, at the cost of the years it takes to earn standing again.

What is built today

piecehow
Sign-up and sign-inA passkey (WebAuthn, ES256) plus an AT Protocol account on our data server: a did:plc and a handle under attest.monster, bound by DNS.
Silent signingOn sign-in your passkey signs a 30-day delegation to a device key that lives in the site's own browser storage. Records are then signed on your device with no prompt. Each site gets its own device key.
Recordsvote, comment, statement, vouch, claim, verification, bookmark, as monster.attest.* records in your repository, each with your inline signature. Subjects: a URL, a DOI, a content hash, or another account. Retracting deletes the record.
IndexFollows the repository firehose, verifies every record it counts, drops deleted accounts. /read, /by/<did>, /handle/<name>, /site/<host>.
CustodyRevoke any session; add a second passkey from a new device, approved by an existing one; remove one with another's signature.
Profiles, vouches, proofsA page per handle; "I know this person" with its cost shown; proof of control over a website, domain, GitHub user or Bluesky handle, verified by the service.
Trust from elsewhereProve a Bluesky handle and your Tangled vouches and follows and your Bluesky follows come in as trust edges of different strengths.
AgentsAn agent asks with its own key; you approve on attest with your passkey, narrowing it if you like. The permission (record kinds as AT Protocol permission strings, a daily limit, an expiry) is public at /agent/<id>. Its records go into your repository marked "via" the agent and count as yours, once. Revoke any time.
Private sign-insWhich sites you sign in to is not published: a sign-in names its site only as a salted hash, and appears in the log only once something signed with it does.
LimitsPer-address and per-session rate limits on writes. Reads carry cache headers for CDNs. No cookies.

Why

Nothing on the web scores the people and outlets that feed us. The founder's phrase for it: "I liken this to the food and drug administration, or to a river; I am being fed pollutants and there isn't even any scoring." PageRank scored emitters once. The platforms took it away and score items, or nothing.

From the builder's side the same gap looks different. A small publication should not have to write its own sign-up, votes and comments, and should not have to hand its readers to a platform that then owns the relationship. Every small service rebuilds the same identity layer, badly, and each rebuild is another silo where reputation cannot travel.

Those are one problem. Signed statements are the anchor. Everything else, scores included, can be rebuilt by anyone from the log. The longer argument, with a fungus in it, is the essay Foundations of Trust.

People and their agents

The internet is changing shape. Trust is moving out of the platforms in the middle and into systems with no center, where people vouch for each other directly and anyone can check the record. And "we" are changing. More of what each of us does online will be done by software acting for us, so a person becomes their own will plus the powers they hand to their agents, and can take back.

That is close to how a company works: each employee has their own badge, a job, limits on what they may sign, and a record of what they did, and the company answers for them. attest gives people the same arrangement with their agents, in public. Each agent has its own key. Your passkey signs what it may do and until when. Everything it writes says so. It earns no trust of its own: a hundred agents vouching add nothing that one does not, because their vouches are yours. In a web full of agents, the useful question is less "is this a person?" than "which accountable person stands behind this?", and that is a question signed records can answer.

What is different about it

We read forty-eight prior efforts before writing a line. Labelers on the AT Protocol, Community Notes, the Ethereum Attestation Service, Nostr reactions, Advogato's trust metric, EigenTrust, SybilGuard, Certificate Transparency, the web of trust, Keybase, the outlet raters. None combines ordinary sign-up with a key the person holds, signed statements about arbitrary URLs and keys, a read endpoint a static page can render, and trust computed by bounded flow with burnable identity. Each of the nearest is missing at least two of those. The flow-based trust math was worked out twenty years ago and shelved because nobody had an adversary worth it.

Other work

Nobody builds this alone, and several of these are worth your time before ours. If you know one we missed, the ways in section says how to tell us.

The full catalogue, 68 entries with the URL read and the date, is in the repository under reference/.

What comes next

attest is the bottom layer: signed statements by people and their agents. Above it comes scoring that follows trust outward from people you choose; above that, tools that tell you how likely something is to be real, and why. The roadmap has what is built, what is next, and the longer list: scores relative to you on any post, voting, place-based attestations, and the projects we are still reading. attest moved onto AT Protocol a day after launch; the changes page explains why.

Ways in

This project is useful in more than one way, and not all of them involve using it.

What it will not do

Lineage

The fuller story, with the people and dates, is on the history page.

Friedman and Resnick, The Social Cost of Cheap Pseudonyms (the newcomer-at-zero result, and the cost we knowingly pay). Cheng and Friedman, Sybilproof reputation mechanisms (no symmetric sybil-proof score exists; asymmetric flow from a source can be). Levien, the Advogato trust metric. Kamvar et al., EigenTrust. Yu et al., SybilGuard. Cao et al., SybilRank. Gyöngyi et al., TrustRank. The AT Protocol label record and NIP-73 target grammar. Community Notes and the per-rater quality weight. Vonnegut, Cat's Cradle, 1963.