dev.cartridge.graph.verification

A Cartridge-specific verification record for studios, developers, publishers, and games. Written by the Cartridge verifier account.

Repository @cartridge.dev did:plc:4mrwcmxk266itsdn33leqljq namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritygraph.cartridge.dev
Indexed

Record

record · key tid

Properties

accountType

requiredstring

Type of verified account.

  • maxLength: 64
  • knownValues: studio | developer | publisher | game

createdAt

requiredstring · datetime

displayName

requiredstring

Display name at time of verification.

  • maxLength: 640

handle

requiredstring · handle

Handle of the verified account at time of verification.

subject

requiredstring · did

DID of the verified account.

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.

  • 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 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.

  • com.emdashcms.experimental.publisher.verification

    record not from the namespace authority

    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.