org.tangled.repo.reserveKey
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "Reserve a repo identity under a DID the caller brings. The knot seals and holds a signing key for the repo DID; the caller publishes the matching public key in that DID's document before calling org.tangled.repo.createRepo with the same DID.",
"input": {
"encoding": "application/json",
"schema": {
"properties": {
"repo": {
"description": "The caller-minted DID to reserve",
"format": "did",
"type": "string"
}
},
"required": [
"repo"
],
"type": "object"
}
},
"output": {
"encoding": "application/json",
"schema": {
"properties": {
"key": {
"description": "Multibase-encoded public signing key the knot holds for this repo identity",
"type": "string"
},
"repo": {
"format": "did",
"type": "string"
}
},
"required": [
"repo",
"key"
],
"type": "object"
}
},
"type": "procedure"
}
},
"id": "org.tangled.repo.reserveKey",
"lexicon": 1
}
Metadata
- DID
-
did:plc:wshs7t2adsemcrrd4snkeqli - CID
-
bafyreic6k4hijnuzhjx3txjqsaxxgov64r25hwqbpiyt5lnps2t3qjdesq - Indexed At
- 2026-10-28 14:06 UTC
- AT-URI
-
at://did:plc:wshs7t2adsemcrrd4snkeqli/com.atproto.lexicon.schema/org.tangled.repo.reserveKey
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
com.atproto.server.reserveSigningKey procedure
Reserve a repo signing key, for use with account creation. Necessary so that a DID PLC update operation can be constructed during an account migraiton. Public and does not require auth; implemented by PDS. NOTE: this en…
-
org.tangled.repo.createRepo procedure
Create a new repository
-
org.tangled.repo.mintToken procedure
Mint a service-auth JWT whose issuer is this repo's DID, signed by the knot that owns the repo's signing key. When calling this, you'll need the same perms as git push, ie. being repo owner/collaborator/knot-admin.