First half of the add-keys flow: read the user's Nostr pubkey via NIP-07 (xlogin or any window.nostr provider), encode it as a Multikey per did:nostr, and display the verificationMethod JSON the user would add to their profile.
No mutations yet — just compute and display. Lets a logged-in user paste it via any client that has write access (databrowser, scripted PUT). B.3 will close the loop with an in-app PATCH via Solid-OIDC.
Acceptance
- "Connect Nostr signer" button detects window.nostr; gracefully degrades if absent
- Shows the hex pubkey and the Multikey-encoded form
- Generates a verificationMethod entry shaped per CID v1, including controller bound to the diagnosed WebID
- Generates the matching authentication / assertionMethod array entries
- Copyable JSON snippet
- Works in current Chromium + Firefox
Out of scope
- Solid-OIDC sign-in / DPoP — that's B.3
- did:nostr DID document construction / publishing — separate concern
- Key rotation UI
First half of the add-keys flow: read the user's Nostr pubkey via NIP-07 (xlogin or any window.nostr provider), encode it as a Multikey per did:nostr, and display the verificationMethod JSON the user would add to their profile.
No mutations yet — just compute and display. Lets a logged-in user paste it via any client that has write access (databrowser, scripted PUT). B.3 will close the loop with an in-app PATCH via Solid-OIDC.
Acceptance
Out of scope