changes a public revision log

Newest first. Decisions and reversals are recorded here as they happen, including the ones that make earlier pages wrong; those pages get corrected, and the correction is logged too. The full working notes are the dated entries in devlog/ in the repository.

2026-11-04 · Sign in and save, in the open

People shown attest asked how to sign in and how to bookmark something, and did not find either inside the folded ☰. Both are now visible on every page: Sign in when you are out, your handle and Save a page when you are in; the ☰ keeps the rest. The home page's button says Sign in or create account instead of Start, the login page says which button a newcomer wants, the tools page is called bookmark a page and leads with the paste-a-link route that needs no setup, and the FAQ opens with those two questions.

2026-10-07 · Agents

An AI agent can now act for a person, within limits the person sets. The agent makes its own key and asks; the person opens the link it shows, checks the code, and approves with their passkey, choosing which kinds of record it may write, how many a day, and for how long. The permission is public at /agent/<id>, written in AT Protocol permission strings, so anyone can see whom an agent acts for and within what bounds. What it writes lands in the person's repository marked "via" the agent and counts as theirs, once. Outside its permission, over its limit, or after it is revoked, it is refused. Agents use plain HTTP and a small client with a command-line tool. This replaces the agent accounts the roadmap proposed on 2026-09-28: an agent has its own key but no account of its own, and the person answers for what it writes. A sign-in made for one website can no longer be used without that website's origin.

2026-10-02 · Where you sign in is private

Signing in to another site through attest no longer tells anyone which site it was. The permission your passkey signs names the site only as a salted hash whose salt stays with that site, and it is published only when something signed with it is published. Profiles no longer list sign-ins; you still see your own, with their sites, on your page. Before today the public log named the site of every sign-in; the entries that named another site have been deleted.

2026-10-02 · Nightly backups

Every account, repository and the index are backed up each night, as consistent snapshots of each database, kept for two weeks with a weekly copy kept for two months. A restore was checked against the live service: the same repositories, the same records.

2026-10-02 · Trustgraphs

Jake Hartnell's Trustgraphs joined the reading room, the history and the roadmap. It computes scores from vouches, flowing from starting accounts a community chooses, and proves them; it is the closest published design to the scoring planned here.

2026-09-29 · Sign in on a phone

Signing in from another site no longer depends on a popup. Where one cannot open, as on many phones and in apps added to the home screen, the site sends you to attest and you come back signed in.

2026-09-29 · Offensive handles refused, without keeping the words

Sign-up now refuses offensive handles, including disguised spellings with digits or repeated letters. The words come from three open-source lists covering English and eleven other languages, read only when the list is built; what the service keeps is their SHA-256 hashes, so no such word appears in its code or on its server. To avoid blocking real people, a word that is also someone's name never blocks, words from other languages that are ordinary English words are dropped, and only English words that never occur inside ordinary English words are caught in the middle of a handle. Against the system dictionary, one proper name in 9,919 is still caught. The check is its own package, handle-guard, in the attest repository, so other sites can use it. Admins can block or allow further words from the admin page, again stored only as hashes.

2026-09-29 · Admin, and a public moderation log

An admin page for the people who run this instance, today one person. Every admin request is signed by the admin's own key, like any record; there is no admin password. Admins can see the service's health, accounts and recent records, reserve handles, and hide a record or an account from attest's counts and pages. Hiding deletes nothing and can be undone, and every hide and unhide is published at /moderation with who did it and why, along with the list of admins.

2026-09-29 · Sign in with your existing handle

A reader asked the right question: does this only work with accounts created on attest's own server? It did. Now anyone with a Bluesky or other AT Protocol account can sign in with their handle. Their own server asks them to approve attest, which requests only permission to publish attest's own record types in their repository, not their posts, follows or messages. They then create a passkey here, so each record carries their own signature as well as their server's. Records go into their repository, where anyone can read them. Tested end to end against a server we run and checked against Bluesky's own server, which accepts the narrow request.

Along the way we found that the official AT Protocol OAuth library for Node, on loading, replaces Node's built-in HTTP engine with a copy from a different version, after which every fetch in the process returned responses without headers. attest now puts Node's own engine back straight after loading it.

2026-09-28 · A reading room

A reading room of papers, specifications and projects on trust and identity, each filed by someone who read it, with their note. It is made of ordinary bookmarks tagged reading-room, so anyone can add to it. A suggested shelf lists books nobody here has filed as read yet.

2026-09-28 · Why a monster

A page on the motive underneath the project: power drifts to centers without anyone deciding it should, centers attract the people who should least hold them, fabricated participation overruns open networks, and the crises that matter most are ecological. The reef rather than the empire; the design rules that follow; what they mean for attest; and what is not yet known. Read it at Why a monster.

2026-09-28 · A home page for people, not engineers

The home page now tells the story before the technology: trust passed hand to hand, three plain steps, and why. Behind it sits one of four paintings. Only if the page is left untouched for a few seconds does it begin to move, then it fades gently from one short clip to the next, and it comes to rest as soon as you scroll or tap. The four, generated with Seedream and Seedance and credited as such, show hands of many ages and origins holding a web of string, a forest's roots and fungal threads connecting its trees, hands tending the earth, and a river crossing borders with its villages joined. They are illustration on purpose; no real person is depicted. Everything technical moved one door away: a docs page groups the material by reader, the guide for integrators is now at /builders, and the menu is down to a handful of items.

2026-09-28 · A history page

A history of the work attest stands on, from Ostrom and PGP's web of trust through reputation economics, trust metrics, tagging, OpenID and OAuth, Keybase, decentralized identifiers, Nostr, AT Protocol and Community Notes to today's work on trust graphs and communities, with the people who did it, the dates, and what each gave us. Every date and name is taken from the linked source.

2026-09-28 · Roadmap reorganised around communities and agents

After reading Kaliya Young, Kevin Triplett and Drummond Reed's work on decentralized trust graphs, the roadmap now states its principles: trust is transitive and contextual; any node can be a community, and a person is one too, acting through agents that deserve their own accounts; mutual vouches count for more; no proof of personhood by biometrics; public by default, with private relationships an open question. The next items follow from them: mutual vouches, agent accounts, communities, then a first version of scores.

2026-09-28 · Bookmarks, tags, and saving from anywhere

Social bookmarking, in the tradition of Delicious and Pinboard, on signed records you keep. A bookmark files a page under your tags, with a title and a note, as a monster.attest.bookmark record in your own repository; filing is not endorsing, and a checkbox adds a separate upvote when you mean it. Save from anywhere: a bookmarklet for computers and iPhones, and on Android, once the site is added to the home screen, "Share → attest" from any app. The save window runs on attest.monster, so the page you are reading never touches your key. Your bookmarks and tags are on your page; everything filed under a word is at /tag/word, most-filed first.

2026-09-28 · Attesting people, not just pages

Now that each person has a page address, the index recognises statements about a person wherever they are made: an upvote or comment on attest.monster/name, on name.attest.monster, on their Bluesky profile (by their attest handle, their DID, or a Bluesky identity they have proven), or on the home page of a site they have proven they control. Profiles have a widget for exactly that, and show what was said about the person elsewhere. The link to the person is fixed when the statement is indexed, so a handle reused later does not inherit it.

2026-09-28 · Handles and public addresses

Handle rules tightened before real sign-ups: 4 to 20 characters, lowercase letters, digits and single hyphens, starting with a letter, because a handle becomes a hostname. Role names, the site's own page names and a few brands are reserved; page and route names are reserved automatically when the server starts, so a new page can never collide with a person. A deleted account's handle is held for a year. People's pages now live at the root, attest.monster/name, beside the site's pages, with /@name and /u/name as aliases and a link to the same account on Bluesky.

2026-09-26 · Accuracy pass

The About, technical, integrator, home and sign-in pages and llms.txt were rewritten where they still described the design before the move to AT Protocol: a single append-only log, records identified by a hash of their JSON, accounts identified by the passkey alone. They now describe what runs: an AT Protocol account per person, records in their repository with an inline signature, an index that follows the firehose. The technical page's threat model gained two honest rows: the service holds the repository signing and rotation keys for accounts it hosts, which is why every record also carries the author's own signature; and what happens if the service stops.

2026-09-26 · Trust edges from elsewhere; deleted accounts drop out; lexicons published

Read-in. When someone proves a Bluesky handle, attest now links that identity and imports the trust edges it has already declared on AT Protocol: Tangled vouches and denouncements, Tangled follows, and Bluesky follows, kept as separate kinds so a scorer can weigh a vouch above a follow. Profiles show which other members vouch for or follow a person elsewhere. Denouncements are kept as evidence and, as with everything negative here, will not propagate. Imports refresh every six hours. Tested on real accounts: one Tangled developer's repository gave 20 vouches, 3 Tangled follows and 607 Bluesky follows in two seconds.

Deleted and deactivated accounts drop out of every count as soon as their data server announces it on the firehose.

Lexicons published. The six monster.attest.* schemas are now records in the service's own repository, with _lexicon.attest.monster pointing at it, so AT Protocol tools can resolve them by name.

2026-09-25 · FAQ and roadmap

An FAQ, led by the question readers ask most: does this need to exist at all. A public roadmap with scores relative to you on any post, voting (and why secret ballots are a separate problem), place-based attestations, and projects we are still reading. The About page's old "what comes next" was replaced by a pointer to it.

2026-09-24 · The index follows the firehose; handles resolve by DNS

The service no longer trusts only what it wrote. It subscribes to its data server's repository stream, verifies each record's inline signature against the repository it sits in, and indexes it; an unsigned record in one of our collections is ignored, and a deleted record is retracted. A record written into a repository by any other client now counts exactly as one written through our widget. That is the property the fold was for.

Handles bind to identities by DNS: each account gets a _atproto.<handle> TXT record with its DID, the AT Protocol way, so Bluesky's resolver already answers for attest.attest.monster. The wildcard certificate for handle hostnames is still not issued by the host's edge; with DNS binding it is no longer needed for resolution.

2026-09-24 · Records now live in repositories

The fold's first working step. Sign-up still makes a passkey; it now also creates a repository account on our AT Protocol data server, with a handle under attest.monster and a did:plc in the public directory. Upvotes, comments, statements, vouches and claims are written into that repository as records in our own lexicons (monster.attest.*), each carrying the person's inline signature from the device key their passkey delegated, in the shared app.certified.signature.defs#inline shape. The service indexes what it wrote; anyone can read the records back from the repository, or from a relay, without us. Retracting deletes the record. The service has a repository of its own for the verifications it signs. The log and the previous record format are gone; the test database was wiped. Every test passes against the live service, including a record verified from public data alone.

Not yet: the index still comes from what we wrote, not from the firehose; handles do not yet resolve over HTTPS on their own hostnames, pending a wildcard certificate; linking an existing Bluesky account is not built. The integrator page describes the new record; the technical page still describes the old log in places and will be corrected in the accuracy pass.

2026-09-24 · The pivot: attest becomes an application on AT Protocol

Two readers of the launch essay changed our architecture within a day of shipping it. One pointed at badge.blue, a specification for signing AT Protocol records, and at socialweb.computer, which reads a vouch graph to decide who may bid for compute, and made the argument that storing attestations as records on the protocol lets everyone borrow meaning from shared lexicons: Tangled's follows and vouches signal different levels of trust and another builder reused them without asking anyone. The other pointed at Hypercerts, which turned out to carry a whole shared vocabulary for attestation on AT Protocol, with badge.blue's signature proofs already in production.

We read them and concluded that most of what we had built or planned already exists there and is better replicated than ours would be: identity with a public directory, signed repositories relayed by a firehose, a shared record vocabulary, and millions of accounts. What does not exist there is what we care most about: statements about URLs, DOIs and file hashes rather than about protocol records; a key the person holds; and trust scored from a root the asker chooses.

So the decision, taken the same night: keep the application and fold the fabric. Sign-up stays a passkey. Every record still carries the person's own inline signature from a device key the passkey delegated. But records now go into an AT Protocol repository, on a data server we host or on the person's own Bluesky account, in the shared record shapes where they fit and in one small lexicon of ours for URL and hash subjects. attest becomes the index, the scorer and the widget over those records. The first spike that night ran a data server on our host, created a real did:plc account, wrote a record in our own collection with an inline signature, and watched it appear on the firehose. The About and technical pages still describe the standalone design in places; they will be corrected page by page as the new one lands, and each correction will be logged here.

What this cost us: one day of building the standalone version, and a launch essay that describes it.

2026-09-23 · Custody, profiles, vouching, proofs, sites

Revoke any session from your own page. Add a second passkey, approved by an existing one; remove one with another's signature. Profiles at /@handle showing who vouched for a key and whom it vouches for. "I know this person" with the cost shown. Proof of control over a website, a domain, a GitHub user or a Bluesky handle, checked and signed by the service's own key. A page per domain with its most-attested pages. Reader feedback added an "Other work" section to About and a table of borrowed practices to the technical page.

2026-09-23 · attest.monster, mascot, essay

The domain, with the old host redirecting so passkeys have one origin. The test database was wiped in the move. The mascot, a creature holding a cat's cradle. The launch essay, Foundations of Trust, on Substack.

2026-09-23 · Pass 1

Passkey sign-up, per-site device keys by delegation, signed records (upvote, comment, vouch, statement, retract) about URLs, an append-only log, plain cacheable reads, a widget for static sites, and an end-to-end test that verifies a record from the log alone. Built in one day from a prior-art catalogue of 48 efforts read the day before. Source public under MIT the same evening, first at anselm/attest, then moved to orbitalfoundation/attest.

2026-09-22 · The catalogue

Forty-eight prior efforts read and tabulated before any code, with the conclusion that nothing combined ordinary sign-up with a held key, signed statements about arbitrary URLs, a read endpoint for static sites, and trust by bounded flow with burnable identity. That conclusion still stands; the pivot above is about where the records live, not about that gap.