Lexicon Garden

build.clovernight.identity.verification

Identity verification status record — proves that a DID has been verified by a trusted verifier.

Repository @studio.pds.clovernight.build did:plc:eylr5g42jkpwyputz3xbgynj namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityidentity.clovernight.build
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

credentialRef

string

Reference to the W3C Verifiable Credential (e.g., a JWT or URN).

  • maxLength: 4096

status

requiredstring

Verification status.

  • knownValues: verified | pending | revoked

verifiedAt

requiredstring · datetime

ISO 8601 timestamp of when verification was performed.

verifierDid

requiredstring · did

DID of the verifier that issued this verification.

Similar lexicons

semantic match

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

  • town.delve.graph.verification

    record not from the namespace authority

    Record declaring a verification relationship between two accounts. Verifications are only considered valid by an app if issued by an account the app considers trusted.

  • app.bsky.graph.verification

    record

    Record declaring a verification relationship between two accounts. Verifications are only considered valid by an app if issued by an account the app considers trusted.

  • ai.newnal.trustsquare.verification

    record not from the namespace authority

    Public, PII-free proof that this account passed identity verification with the Newnal verifier. The attestation is a compact JWS signed by the issuer; the AppView rejects records whose signature or payload does not match.

  • dev.keytrace.claim

    record

    An identity claim linking this DID to an external account

  • 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