FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Served did:nostr docs use `Multikey` but `@context` does not define it (use cid/v1) · Issue #568 · JavaScriptSolidServer/JavaScriptSolidServer · GitHub

Repository navigation

Served did:nostr docs use Multikey but @context does not define it (use cid/v1) #568

Closed

Description

src/idp/well-known-did-nostr.js serves DID documents with "type": "Multikey" + publicKeyMultibase, but the @context is ["https://w3id.org/did", "https://w3id.org/nostr/context"] — neither entry defines Multikey, and https://w3id.org/did returns text/html (not a JSON-LD context). So the served documents do not fully JSON-LD-expand.

Multikey / publicKeyMultibase are defined in Controlled Identifiers v1.0 (https://www.w3.org/ns/cid/v1). Notably jss already uses that context in src/keys/provision.js:141, so this is also an internal inconsistency.

Fix: change the served DID-doc @context to ["https://www.w3.org/ns/cid/v1", "https://w3id.org/nostr/context"].

Mirrors the spec change in nostrcg/did-nostr#91 (issue nostrcg/did-nostr#90). Safe: a grep finds no code asserting the literal @context value; auth/resolution match on the verification method / pubkey, not the context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    diddid:nostr method spec + implementation alignment

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL