What

did:nostr 0.1.1 is published (spec, v0.1.0...v0.1.1 diff). It is a one-line change to the DID document @context, which must now lead with the DID Core context:

"@context": [
  "https://www.w3.org/ns/did/v1",
  "https://www.w3.org/ns/cid/v1",
  "https://w3id.org/nostr/context"
]

This follows discussion at the W3C Credentials CG — DID Core normatively requires the @context to lead with https://www.w3.org/ns/did/v1 (nostrcg/did-nostr#136, fixed by nostrcg/did-nostr#139).

Where

One place — the .well-known DID document builder:

• src/idp/well-known-did-nostr.js:501 — '@context': ['https://www.w3.org/ns/cid/v1', 'https://w3id.org/nostr/context'] → prepend 'https://www.w3.org/ns/did/v1'

Verified live: https://nostr.social/.well-known/did/nostr/<pubkey>.json currently serves the old ordering.

Explicitly out of scope (correct as they are — DID Core's requirement applies to DID documents only):

• src/keys/provision.js:141 — standalone Multikey object; a Controlled Identifier resource, cid/v1 is the right context
• src/webid/profile.js — WebID profile per LWS 1.0, built on CID v1.0; cid/v1 vocabulary is correct

Compatibility

Documents in the previous form are unlikely to break anything — both orderings expand to the same terms under JSON-LD (verified with jsonld.js in nostrcg/did-nostr#136). The new form is DID Core-conformant and future-proofed for the DID 1.1 transition (tracked in nostrcg/did-nostr#138).

The did:nostr conformance test vectors are updated to the new ordering: https://github.com/nostrcg/did-nostr/tree/gh-pages/test-vectors