dev.cartridge.graph.verification
A Cartridge-specific verification record for studios, developers, publishers, and games. Written by the Cartridge verifier account.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | graph.cartridge.dev |
| Indexed |
Record
record · key tidProperties
Type of verified account.
maxLength: 64knownValues: studio | developer | publisher | game
Display name at time of verification.
maxLength: 640
Handle of the verified account at time of verification.
DID of the verified account.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
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
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.
-
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.
-
Check whether a DID or handle has been verified by the Cartridge verifier. Does not require authentication.
-
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.