René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Explore did:nostr: identity support","articleBody":"## Background\n\nNostr uses secp256k1 keypairs for identity. A `did:nostr:\u003cpubkey\u003e` could serve as a decentralized WebID without requiring an HTTP-hosted identity document.\n\n## What Would Be Needed\n\n### Client (solid-oidc.js)\n- Already accepts any `webid` claim - minimal changes needed\n- May need DID resolution if dereferencing the WebID\n\n### IDP (Server)\nA Nostr-OIDC bridge that:\n1. Presents a challenge (random nonce)\n2. User signs with their Nostr private key (nsec)\n3. Bridge verifies signature against public key (npub)\n4. Issues standard OIDC tokens with `webid: \"did:nostr:\u003cpubkey\u003e\"`\n\n## Possible Approaches\n\n1. **Patch existing IDPs** (CSS, JSS) - add Nostr auth flow\n2. **Standalone Nostr-OIDC bridge** - minimal service that speaks OIDC but authenticates via Nostr\n3. **Client-side DPoP with Nostr keys** - skip OIDC, use Nostr keys directly for DPoP\n\n## Questions\n\n- Should the `webid` be `did:nostr:\u003cnpub\u003e` or `did:nostr:\u003chex-pubkey\u003e`?\n- How to handle DID document resolution?\n- Could NIP-05 identifiers map to WebIDs?\n\n## References\n\n- [DID Nostr Method](https://github.com/nostr-protocol/nips) (if formalized)\n- [Solid-OIDC Spec](https://solidproject.org/TR/oidc)\n- [Nostr NIP-07](https://github.com/nostr-protocol/nips/blob/master/07.md) - browser extension signing","author":{"url":"https://github.com/melvincarvalho","@type":"Person","name":"melvincarvalho"},"datePublished":"2025-12-30T07:30:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1/solid-oidc/issues/1"}