FAQ asked by real readers
How do I sign in?
Tap Sign in at the top right of any page. New here: type the handle you would like and tap Create account; your phone's face or fingerprint unlock becomes your key, and there is no password or email. Already on Bluesky: type your Bluesky handle in the second box instead.
How do I bookmark a page?
Once signed in, tap Save a page at the top right and paste the link. For one click from any page, set up the button for your browser, or your phone's share menu on Android.
Does this need to exist? What does it do that nothing else does?
Much of the machinery already exists: AT Protocol gives identity, signed repositories and a firehose; badge.blue and Hypercerts give a shared way to sign records; Tangled has vouches. We folded onto that stack a day after launch rather than compete with it (see changes). What attest adds is narrow, and we think it is real:
- Statements about the open web. Records on AT Protocol are mostly about other records and accounts. attest's records are about URLs, DOIs and file hashes: this article, this paper, this photograph. That is where most of what reaches us actually lives.
- A key you hold, on every record. You sign in with a passkey. AT Protocol leaves sign-in to each hosting server, and the reference server uses a password. Here your passkey signs a permission for a device key, and that key signs every record inline. The record carries your own signature, not only the server's, so it can be checked with your key alone.
- Agents that answer to someone. An agent gets its own key and a public permission your passkey signed: what it may write, how much, until when. Its records count as yours. See below.
- Sign-in and attestations as a drop-in. One script tag gives a static site or a small project sign-up, votes, comments and vouches, with no accounts, passwords or database of its own. That is the reason it was built: every one of the founder's projects was re-implementing auth.
- Scores relative to you. When scoring lands, every answer is "trusted by people you trust", computed from a starting key you choose, never a platform number called "trustworthy".
Could it just not exist? Yes, if Bluesky, Tangled or the Hypercerts community adds a shared lexicon for URL and hash subjects and an index that scores from a root. If that happens we would rather join them than duplicate them, and we say so on the About page. Until then, this is one working version of the idea, in public, with its reasoning written down.
Do I need a Bluesky account?
No, but you can use one. If you already have a Bluesky or other AT Protocol account, sign in with your handle: your own server asks you to approve attest, and attest asks only to publish its own kinds of record (bookmarks, votes, comments, vouches, claims, statements) in your repository, nothing about your posts, follows or messages. You then create a passkey here, so everything you sign carries your own signature too. Without an account, signing up creates one for you on our server, with a handle like you.attest.monster.
What names can I have, and where is my page?
A handle is 4 to 20 lowercase letters, digits and single hyphens, starting with a letter, and it is unique: it becomes name.attest.monster, a real hostname and your AT Protocol handle. Your page is attest.monster/name, beside the site's own pages; /@name and /u/name work too, and Bluesky shows you at bsky.app/profile/name.attest.monster. Names used by the site's pages, roles such as admin or support, and a few brands are reserved, so nobody can pass as the site or as a well-known project. Handles that are offensive in English or several other languages are refused; the lists are kept only as hashes, and admins can allow a name the lists catch by mistake. A handle freed by a deleted account is held for a year, so nobody can step into a departed person's name; even after that, the newcomer gets a new identity and inherits none of the old one's records. What identifies you underneath is a DID; the handle is a readable label for it.
Who holds my key?
Your device does. The passkey is created and kept by your phone or computer, and synced by Apple or Google if you use their passkey sync. We store only its public half. The repository account behind it has a server-side password you never see; that part is held by us, the way any AT Protocol host holds it, which is why every record also carries your own signature.
Does attest care which device or app holds my passkey?
No. attest asks the device nothing about itself and accepts any passkey manager, any operating system, or a hardware security key. The WebAuthn standard lets a site demand proof of an approved device; attest does not use it, and critics of passkeys are right that it could be misused elsewhere.
What if I lose my phone?
Add a second passkey from another device now, on your own page. With one passkey, a lost device is a lost account. Key export is planned.
What if attest shuts down?
Your identity is a did:plc in a public directory, not a row in our database. Your records are in an AT Protocol repository that relays copy. The key that controls the accounts made here is backed up off our server, and the data is copied nightly, so the service can move to another host. The records you signed stay verifiable by anyone with your key, with or without us.
Is this a blockchain? A token?
No to both. It runs on signed records in public repositories on ordinary servers, and there is nothing to buy.
Is everything public?
What you sign is. That is deliberate: a trust graph only works if anyone can check it. Anything derived from it, counts and scores included, is public too. Do not sign what you would not say in public.
Can people see which sites I sign in to with attest?
No. When you sign in to another site through attest, your passkey signs a permission for that site's key, and the permission names the site only as a salted hash. The salt stays with that site, so nobody else can work out which site it was. Signing in alone publishes nothing at all: the permission enters the public log only when something signed with it is published, such as a vote or a comment, and then still without the site's name.
What you then publish there is public as usual. A vote or comment on a page names that page, because that is the point of it. attest's own server knows which site each sign-in is for, so it can refuse a key used somewhere else and show you your own sign-ins on your page. Sign-ins made before October 2, 2026 named the site openly; those that named another site have been deleted.
Do you use cookies? Why is there no cookie notice?
No cookies, and nothing that tracks you, so there is nothing to ask consent for. The site keeps three things on your own device, all needed for what you asked it to do: your sign-in session and the handle you last used, in the browser's local storage, and the key that signs your records, in its database, marked so that even the page cannot read it out. None of it is sent to us. Signing out removes the session. On another site that embeds attest, those three live in that site's storage, not ours.
Can I delete something?
You can retract it, which deletes it from your repository and from our counts. Copies that relays or other services already took may persist; that is true of all public posting on AT Protocol.
Can an AI agent act for me?
Yes, within limits you set. The agent makes its own key and asks. It shows you a link and a code; you open the link on attest, check the code, and approve with your passkey, choosing what it may write, how many records a day, and for how many days. You can narrow what it asked for, and revoke it on your page at any time.
The permission is public. Anyone who sees something your agent signed can look up that it acts for you, within what bounds, and whether it still may. What it writes goes into your repository, marked as written via the agent, and counts as yours, once: a hundred agents add no more trust than one. An agent never earns trust of its own. The limits are written as AT Protocol permission strings, so other software can read them; builders, see how an agent asks.
Where is this going?
attest is the bottom of a stack. It gathers signed statements: who vouched for whom, who saved or upvoted what, who said what about a page, and which agent did it for whom. Above that sits scoring, which follows trust outward from people you choose and gives little weight to whatever nobody you trust stands behind. Jake Hartnell's Trustgraphs is a working example of that layer, with scores anyone can check. At the top are the tools you read with, which can tell you how likely something is to be real, and why. The bottom layer works today; the score is next.
Is there a score yet?
Not yet. Counts are raw today and say so. Scoring from a root you choose is the next large piece on the roadmap, and it waits until there are real vouches to score.
Do you check that I am human?
No, on purpose. Proving personhood usually means biometrics or an identity welded to your body, and we think that is riskier than the problem it solves. People act through agents, and agents can act here too, under a public permission from the person who answers for them. Anyone may attest that they have met you in person, and that counts like any other statement, from whoever makes it.
What stops someone making a thousand fake accounts?
Nothing stops them making the accounts. What will stop them mattering, once scoring lands, is that trust flows from a key or community you chose, through vouches and memberships, weaker at each step and with a limit on how much each node can pass on. A cluster that nobody you trust has vouched for will have no reach from where you stand. Newcomers start at zero on purpose.
Can I throw away an identity and start again?
Yes. Reputation belongs to a key, not a person. Starting again means starting at zero, and earning standing back takes time. That cost is what makes everyone else's standing mean something.
Can I use it on my site or app?
Yes: the integrator page has the script tag, the API and the record format. The changes page records every change that matters.
Is it open source? Who runs it? What does it cost?
MIT licensed, at github.com/orbitalfoundation/attest. Run by Anselm Hook under the Orbital Foundation, built with Claude. Free. Donations to anselm.eth.
Why "monster"?
Because we think it will take monsters to fight monsters: centers that attract predators, floods of fabricated voices, and crises that go unanswered while attention is spent elsewhere. The one we are building is meant to be many small hands on the same string. The mascot holds a cat's cradle, after Vonnegut, for the idea that a thing can be made entirely of its relationships. The longer answer is Why a monster.
How early is this?
It went live on 2026-09-23 and was rebuilt on AT Protocol the next day. Test data was wiped twice in that first week; the data is now backed up nightly. Breaking it now, and telling us, is one of the most useful things you can do.
attest and OpenVTC
Written after a week with the OpenVTC team, 2026-11-08.
What is a DID?
A Decentralized Identifier is a name for something that keys control. It looks like did:plc:abc… and it resolves to a small document listing the public keys allowed to sign for it and the addresses where it can be reached. The part after did: says where that document lives and who may change it. A did:key is the key itself and can never change. A did:web is a file on a domain. A did:webvh is that file with a tamper-evident history, so it can move domains and keep its name. A did:plc, which attest accounts use, is an entry in one public directory that the account's rotation keys control. The syntax is shared; the trust is not. The question to ask of any DID is who runs the place its document lives, and what happens when they stop.
What is AT Protocol?
The protocol under Bluesky. Every account has a DID, a handle that is a domain name, and a repository of signed records on a hosting server of its choice. Relays republish every repository as one public stream, and anyone can fetch a repository and check each record against the account's keys. attest accounts are AT Protocol accounts on our server; attest records are typed records in those repositories, which is why you can take them with you.
What is OpenVTC?
A Linux Foundation lab, with specifications at Trust over IP and software from the First Person Project, for communities built on cryptographic membership. Each person has an agent, a server-side program that holds their keys, mints their identifiers and signs for them. Each community is a server that admits members, issues them membership credentials, and runs rooms, directories and polls behind those credentials. Relationships between people are private credentials exchanged pairwise. One of its architects put the difference on a slide: a website is an anonymous, one-way publishing endpoint; a community in their system is an accountable, membership-gated trust endpoint.
How do the two differ?
AT Protocol is the web with signatures. Public by default, readable and verifiable by anyone, with large aggregators in the middle because the design wants them there. OpenVTC is a federation of clubs with cryptographic membership cards: private by default, readable by members, and with no global directory or stream at all. One has years of production use and tens of millions of accounts. The other is at version 0.x, and its own documentation marks much of it unverified.
Which is more decentralised?
Each is, in a different place. AT Protocol has one global dependency, the directory that holds did:plc documents, and one large relay most people read through. OpenVTC has no global dependency by design. A person on AT Protocol depends on one hosting server, which they can leave. A person on OpenVTC depends on an agent host, an identifier host and a message relay, each of which they can in principle leave. Fewer points of failure is true of the OpenVTC network and not of the OpenVTC person. For attest the deciding fact is a different one: our records are statements about the open web, and strangers outside any community must be able to check them. That needs the public, verifiable kind of network.
Can OpenVTC do passkey sign-in the way attest does?
Not the part that matters. In attest your passkey is the root of your keys: it signs the 30-day permission for each device, and anyone can check that signature against your published public key. No server holds a key that can act as you. In OpenVTC the root keys live in your agent, and the agent signs documents; a passkey can log you in to the agent or confirm a step, and their browser plugin can put one in your identifier for signing in to websites. Their own security notes say it: passkeys authenticate a person to a service and do not sign documents. The trade runs the other way too. Our design loses the account with the last passkey; theirs survives devices because the agent holds everything, at the price of trusting the host.
Will attest use OpenVTC?
Where the shapes match. attest stays on AT Protocol, where its public records belong. attest also holds an agent and an identity in their system, so the two can meet. The meeting point is the vouch: an accountable statement between two parties is exactly what their system is built to carry.