monster.attest.claim
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "The author claims control of a website, domain, or handle on another service. A verifier places attest-proof:<record cid> where only the controller could and issues a monster.attest.verification. Record key: a base32 sha256 of the subject/target, so there is one per author per subject.",
"key": "any",
"record": {
"properties": {
"createdAt": {
"description": "Client-declared time of the statement.",
"format": "datetime",
"type": "string"
},
"signatures": {
"description": "Inline signatures per the ATProtocol Attestation Specification; attest requires one from the author's device key (did:key, delegated from their passkey).",
"ref": "app.certified.signature.defs#list",
"type": "ref"
},
"target": {
"description": "https://<origin>/ for a website, dns:<domain>, github:<user>, bsky:<handle>, or another service:<handle> pair.",
"maxLength": 2048,
"type": "string"
}
},
"required": [
"target",
"createdAt"
],
"type": "object"
},
"type": "record"
}
},
"id": "monster.attest.claim",
"lexicon": 1
}
Metadata
- DID
-
did:plc:tqeqvx3hcgzg5uvgogwkm7lk - CID
-
bafyreicprj2xvhlveqp4jev7m3uryeqmmctgpjfsqh3jbx746a4ufbwgvi - Indexed At
- 2026-09-26 14:10 UTC
- AT-URI
-
at://did:plc:tqeqvx3hcgzg5uvgogwkm7lk/com.atproto.lexicon.schema/monster.attest.claim
Referenced Schemas (1)
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A verifier's statement that it checked a claim and found the proof token in place. Issued by any account, including the attest service's own; trusted as far as the verifier is.
-
A signed public statement by the author, optionally about a subject.
-
'I know this person': the author vouches for another account. Vouching costs the voucher in trust computations. Delete to retract. Mirrors sh.tangled.graph.vouch where a subject is known there. Record key: a base32 sha2…
-
An upvote of a URL, DOI or content hash. One live vote per author per subject; delete the record to retract. Record key: a base32 sha256 of the subject/target, so there is one per author per subject.
-
A signed public comment on a URL, DOI or content hash, optionally anchored to a passage.