com.babesky.graph.verification
A verified creator attestation issued by Babesky. Records are written by Babesky's service DID (did:plc:qtapiembzpxlzsiagnc7eyy3) into its own repository, pointing at the subject's DID. Validity is dynamic: the handle and displayName must still match the subject's current values. Records must be deleted when a creator is removed from Babesky's database.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | graph.babesky.com |
| Indexed |
Record
record · key tidProperties
Display name of the creator at time of verification. Used for ongoing validity checks.
maxGraphemes: 64
Handle of the creator at time of verification. Used for ongoing validity checks.
DID of the verified creator.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
app.bsky.graph.verification
recordRecord declaring a verification relationship between two accounts. Verifications are only considered valid by an app if issued by an account the app considers trusted.
-
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.
-
A Cartridge-specific verification record for studios, developers, publishers, and games. Written by the Cartridge verifier account.
-
Verification claim by one DID about another's status as a trusted EmDash plugin publisher. Modeled on Bluesky's app.bsky.graph.verification shape but in EmDash's own namespace so the semantics are scoped to plugin publishing. EXPERIMENTAL: shape may change before stabilisation.
-
a vouch on atvouch.dev. the rkey of the record must be equal to the subject of the record, which must be a did. records that do not follow this should be considered invalid