Use CID v1.0 @context in served did:nostr docs so Multikey is defined - #569
melvincarvalho merged 2 commits into
Conversation
Sorry, something went wrong.
There was a problem hiding this comment.
Pull request overview
Updates the served did:nostr DID document JSON-LD context to use the Controlled Identifiers v1.0 context so that Multikey / publicKeyMultibase are properly defined, aligning served documents with the project’s existing Multikey document shape.
Changes:
- Switch DID document @context from https://w3id.org/did to https://www.w3.org/ns/cid/v1 in the did:nostr well-known handler.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
| return { | ||
| '@context': ['https://w3id.org/did', 'https://w3id.org/nostr/context'], | ||
| '@context': ['https://www.w3.org/ns/cid/v1', 'https://w3id.org/nostr/context'], | ||
| 'id': did, |
There was a problem hiding this comment.
Fixed in 114d787.
Sorry, something went wrong.
|
|
Sorry, something went wrong.
Bundles three fixes merged since 0.0.208: - fix(nostr): NIP-98 payload hash verifies the raw request bytes instead of a re-serialization, so binary/whitespace-sensitive bodies validate (#573, closes #565) - feat(idp): served did:nostr documents use the CID v1.0 @context so Multikey / publicKeyMultibase are actually defined (#569) - feat(cli): `jss start` shifts off a busy port (Vite-style) instead of crashing on EADDRINUSE, and prints an openable banner URL (#574, closes #557)
Closes #568.
src/idp/well-known-did-nostr.js serves DID documents with "type": "Multikey" + publicKeyMultibase, but the @context (https://w3id.org/did + nostr/context) defines neither, and https://w3id.org/did returns text/html rather than a JSON-LD context.
Multikey / publicKeyMultibase are defined only in Controlled Identifiers v1.0 (https://www.w3.org/ns/cid/v1) — which jss already uses in src/keys/provision.js:141, so this also removes an internal inconsistency. Mirrors nostrcg/did-nostr#91. Safe: nothing asserts the literal @context; auth/resolution match on the verification method, not the context.