did:key
A did:key identifier carries its own public key inside the string, so there is nothing to look up anywhere. ~alter decodes the key locally and asks you to sign a one-time challenge with the matching private key. It is the only connector here that makes no network request at all, which means there is no server, host or registry involved in proving it.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Sign anything other than the single challenge you are shown.
- •Reconstruct your private key from the identifier or the signature.
- •Reach any credential, wallet or service that uses the same key elsewhere.
- •Contact any resolver, registry, or third party. Nothing leaves ~alter during this proof.
- •Surface your did:key pairing to any third party without a separate consent row scoped to that recipient.
The OAuth or attestation scope we request is the minimum required to recognise the pattern described in What we read. Anything beyond that is structurally refused at the connector boundary, not promised by trust. How pairing works.
What we read
- The did:key identifier you provide.
- The public key decoded from that identifier, entirely locally.
- A signature over a single-use challenge, verified once and then discarded.
What we don't read
~Alter explicitly refuses these fields even when the OAuth scope or API permits them. Every refusal is enforced at the connector boundary, not by trust.
- Your private key or seed, neither of which is ever requested or transmitted.
- Other identifiers derived from the same key material.
- Verifiable credentials issued to or by this key.
- Any linkage between this key and a wallet address, unless you attest that separately.
- Anything at all over the network, since this connector makes no request.
Where it lives
The attested identifier and tier badge sit in ~alter's pairing ledger keyed to your ~handle. The challenge is single-use and is consumed the moment it is verified. Revoking removes the identifier from your pairing surface immediately.
How to revoke
Revocation is immediate. Ask the AI client you paired through to revoke this connector, or revoke it from your consent surface over the same connection. Either path revokes the provider token, stops all further reads, and purges the derived signals this connector fed into your identity vector. An audit row records the revocation.
One thing is kept on purpose. The connector retains a record that this account was paired and when it was disconnected, so the same account cannot be unpaired and re-paired in quick succession to churn your identity vector. That cooldown record holds the raw profile snapshot until the window passes. It is never read into a new signal while disconnected, and it is not shared with anyone.
Prefer the command line? The CLI is the optional deeper path and revokes the same connector:
CLI (optional)
alter unpair did-keyPairing this connector does not enrol you in any matching, ranking, or matching surface. Every downstream use requires its own consent row. See the consent model.