org.tangled.repo.reserveKey

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.

Repository @tangled.org did:plc:wshs7t2adsemcrrd4snkeqli namespace authority
Details · procedure
Kindprocedure
Authorityrepo.tangled.org
Indexed

Procedure

procedure · POST

Input

application/json

repo

requiredstring · did

The caller-minted DID to reserve

Output

application/json

key

requiredstring

Multibase-encoded public signing key the knot holds for this repo identity

repo

requiredstring · did

Similar lexicons

semantic match

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

  • 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 endpoint may change when full account migration is implemented.

  • Create a new repository

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