Lexicon Garden

com.blueyvatar.attestation

Written to the service repo. The service's result for one com.blueyvatar.claim.

Repository @blueyvatar.com did:plc:jkfpo6wxvqyf6nzp3bmrkszh not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityblueyvatar.com
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

createdAt

requiredstring · datetime

method

string

Verification method. Per-platform methods are an open item (spec section 13).

  • maxLength: 64

result

requiredstring
  • knownValues: verified | failed | revoked

subject

requiredref
Reference
  • lex:com.atproto.repo.strongRef

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • monster.attest.verification

    record not from the namespace authority

    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.

  • network.attested.payment.proof

    record

    A remote attestation record stored in the attestor's repository (creator or broker). Referenced via com.atproto.repo.strongRef in the payment record's signatures array. The attestation CID is computed per the badge.blue spec from the payment record, attestation metadata, and the repository DID — meaning a record copied to a different repository automatically invalidates all its attestations.

  • agency.portable.attestation

    record

    An attestation by a verifier that a subject atproto account is linked to an identity, community, or role in an external service. Paired with a matching agency.portable.membership record on the subject's PDS.

  • network.attested.proof

    record not from the namespace authority

    A remote attestation proof: a standalone record in the attestor's repository that binds, via a canonical attestation CID, to a subject record living elsewhere. Referenced from the subject's `signatures` array via com.atproto.repo.strongRef. The `cid` is computed from the subject record (signatures stripped) with this record's metadata (cid/signature/signatures stripped, `repository` = subject's repo DID added) inserted as $sig, DAG-CBOR + SHA-256 + CIDv1. Verifiers recompute that CID and require

  • uk.co.bstools.alias.test.attestation

    record not from the namespace authority

    The authoriser confirms it verified the referenced alias link record.