nostr Community Group - Activity

GitHub

nostrcg/did-nostr

• 2 issues opened.

  • 1 October 2026

    Test vectors for the additive-tweak case the parity note describes (normalise once, tweak, 0x03 arising) nostrcg/did-nostr#146, by @melvincarvalho.

  • 1 October 2026

    parity-model.md forbids 0x03, but the spec allows it: reconcile the explainer with the spec nostrcg/did-nostr#144, by @melvincarvalho.

• 1 issue closed.

  • 1 October 2026

    parity-model.md forbids 0x03, but the spec allows it: reconcile the explainer with the spec nostrcg/did-nostr#144.

• 1 issue received 1 new comment.

  • 1 October 2026

    parity-model.md forbids 0x03, but the spec allows it: reconcile the explainer with the spec nostrcg/did-nostr#144 (1 comment by @melvincarvalho)
• 2 pull requests opened.

  • 1 October 2026

    test-vectors: additive-tweak case (normalise once, tweak, 0x03 arising, signing key) nostrcg/did-nostr#147, by @melvincarvalho.

  • 1 October 2026

    parity-model.md: allow 0x03 as the spec does; README links the companion notes nostrcg/did-nostr#145, by @melvincarvalho.

• 1 pull request merged.

  • 1 October 2026

    parity-model.md: allow 0x03 as the spec does; README links the companion notes nostrcg/did-nostr#145.

Participants

• 1 participant joined.

  • 31 July 2026

    Yen-Lin (mashbean) Huang joined.

GitHub

nostrcg/did-nostr

• 4 issues opened.

  • 11 July 2026

    Invalid npub in the "Relationship with Nostr npubs" example mapping nostrcg/did-nostr#141, by @melvincarvalho.

  • 9 July 2026

    Track CCG/DID WG response: did/v1 → did/v1.1 context transition practice nostrcg/did-nostr#138, by @melvincarvalho.

  • 1 July 2026

    Exploratory: key recovery for did:nostr via the CCG DID Recovery model (same-key, immutability-preserving) nostrcg/did-nostr#137, by @melvincarvalho.

  • 1 July 2026

    @context must lead with the DID context (did/v1.1), not cid/v1 — DID Core conformance nostrcg/did-nostr#136, by @melvincarvalho.

• 3 issues closed.

  • 26 July 2026

    create a Primer nostrcg/did-nostr#29.

  • 26 July 2026

    Invalid npub in the "Relationship with Nostr npubs" example mapping nostrcg/did-nostr#141.

  • 26 July 2026

    @context must lead with the DID context (did/v1.1), not cid/v1 — DID Core conformance nostrcg/did-nostr#136.

• 4 issues received 8 new comments.

  • Latest comment 1 July 2026

    @context must lead with the DID context (did/v1.1), not cid/v1 — DID Core conformance nostrcg/did-nostr#136 (5 comments by @amir-hameed-mir, @melvincarvalho)

  • 26 July 2026

    Track CCG/DID WG response: did/v1 → did/v1.1 context transition practice nostrcg/did-nostr#138 (1 comment by @melvincarvalho)

  • 1 July 2026

    Use case: Self-sovereign identity for AI agents (auth + payments in one key) nostrcg/did-nostr#112 (1 comment by @melvincarvalho)

  • 1 July 2026

    Exploratory: key recovery for did:nostr via the CCG DID Recovery model (same-key, immutability-preserving) nostrcg/did-nostr#137 (1 comment by @melvincarvalho)
• 4 pull requests opened.

  • 26 July 2026

    Bump spec version to 0.1.1 nostrcg/did-nostr#143, by @melvincarvalho.

  • 12 July 2026

    Fix invalid npub in the npub-relationship example mapping nostrcg/did-nostr#142, by @melvincarvalho.

  • 9 July 2026

    Add a did:nostr Primer nostrcg/did-nostr#140, by @melvincarvalho.

  • 9 July 2026

    Lead @context with did/v1 for DID Core conformance nostrcg/did-nostr#139, by @melvincarvalho.

• 4 pull requests merged.

  • 26 July 2026

    Bump spec version to 0.1.1 nostrcg/did-nostr#143.

  • 26 July 2026

    Add a did:nostr Primer nostrcg/did-nostr#140.

  • 26 July 2026

    Fix invalid npub in the npub-relationship example mapping nostrcg/did-nostr#142.

  • 26 July 2026

    Lead @context with did/v1 for DID Core conformance nostrcg/did-nostr#139.

nostrcg/http-schnorr-auth

• 1 issue opened.

  • 1 July 2026

    Roadmap: next steps after did:nostr 0.1 — fidelity NIP-98 spec + test vectors, then W3C integration nostrcg/http-schnorr-auth#27, by @melvincarvalho.

• 1 pull request opened.

  • 9 July 2026

    Fix invalid JSON in test-vectors.json (drop stray 'Test Public Key' line) nostrcg/http-schnorr-auth#28, by @melvincarvalho.

nostrcg/schema

• 1 issue received 1 new comment.

  • 6 July 2026

    Add lightweight discovery predicate: map seeAlso → rdfs:seeAlso in the context nostrcg/schema#19 (1 comment by @TallTed)

Reports

• 1 report published.

  • 30 June 2026

    Nostr DID Method Specification published as a draft report.

GitHub

nostrcg/did-nostr

• 29 issues opened.

  • 30 June 2026

    Publish as a W3C Community Group Draft Report (specStatus CG-DRAFT) — cut 0.1 nostrcg/did-nostr#134, by @melvincarvalho.

  • 30 June 2026

    modified example value is off by 20 min (1737906600 = 15:50:00Z, not 15:30:00Z); also #relay vs #relay1 nostrcg/did-nostr#131, by @melvincarvalho.

  • 30 June 2026

    Verifiable Credentials with did:nostr (Data Integrity + BIP-340 Schnorr) — separate layer nostrcg/did-nostr#130, by @melvincarvalho.

  • 30 June 2026

    Standardize on relative verification-relationship references (#key1) across spec, vectors, implementations nostrcg/did-nostr#128, by @melvincarvalho.

  • 30 June 2026

    Make the .well-known HTTP resolution path (incl. .json suffix) normative nostrcg/did-nostr#127, by @melvincarvalho.

  • 30 June 2026

    Reframe Update/Delete operations: document is mutable via the event layer; deactivation is an open item nostrcg/did-nostr#126, by @melvincarvalho.

  • 30 June 2026

    Document the resource model: subject vs document, httpRange-14, ETag/Last-Modified vs in-graph provenance (standalone explainer) nostrcg/did-nostr#123, by @melvincarvalho.

  • 30 June 2026

    Deprecate `profile.timestamp` in favor of document-level `modified` nostrcg/did-nostr#117, by @melvincarvalho.

  • 19 June 2026

    Use case: Verifiable content provenance and authenticity (signed, timestamped authorship) nostrcg/did-nostr#115, by @melvincarvalho.

  • 19 June 2026

    Use case: Censorship-resistant identity (no DNS, no ledger, no platform to deplatform) nostrcg/did-nostr#114, by @melvincarvalho.

  • 19 June 2026

    Use case: Identity with native payments (one key for who-you-are and money) nostrcg/did-nostr#113, by @melvincarvalho.

  • 19 June 2026

    Use case: Self-sovereign identity for AI agents (auth + payments in one key) nostrcg/did-nostr#112, by @melvincarvalho.

  • 19 June 2026

    Use case: First-class interop with the W3C DID/CID/VC ecosystem nostrcg/did-nostr#111, by @melvincarvalho.

  • 19 June 2026

    Use case: One identity across ecosystems (bridges to Solid, Verifiable Credentials, fediverse) nostrcg/did-nostr#110, by @melvincarvalho.

  • 19 June 2026

    Use case: Decentralized single sign-on (one key, sign in anywhere) nostrcg/did-nostr#109, by @melvincarvalho.

  • 19 June 2026

    Use case: Identity at web scale (CDN-cacheable resolution, did:nostr as a cache over relays) nostrcg/did-nostr#108, by @melvincarvalho.

  • 19 June 2026

    Use case: Portable social graph (followers that survive app switches) nostrcg/did-nostr#107, by @melvincarvalho.

  • 19 June 2026

    Design: provenance model (in-graph source-derived times + content-hash ETag + blocktrails), superseding `Nostr-Timestamp` nostrcg/did-nostr#106, by @melvincarvalho.

  • 19 June 2026

    Specify whether key transformation validates the identifier as a valid secp256k1 x-only key (x < p, on-curve) nostrcg/did-nostr#105, by @melvincarvalho.

  • 19 June 2026

    `FollowsEndpoint` is underspecified — mark at-risk and design the response format before publication nostrcg/did-nostr#104, by @melvincarvalho.

  • 19 June 2026

    `Nostr-Timestamp` header is redundant with `Last-Modified` — mark at-risk before publication nostrcg/did-nostr#103, by @melvincarvalho.

  • 17 June 2026

    Document the x-only vs Multikey parity model (0x02/0x03) as a standalone explainer (CG note / blog post) nostrcg/did-nostr#102, by @melvincarvalho.

  • 16 June 2026

    Publication readiness: path to a W3C Community Group Draft Report nostrcg/did-nostr#100, by @melvincarvalho.

  • 16 June 2026

    Bump version to 0.0.11 nostrcg/did-nostr#98, by @melvincarvalho.

  • 16 June 2026

    Spec is unstyled in Brave: Brave blocks w3.org assets the server explicitly permits (optional: vendor CSS same-origin) nostrcg/did-nostr#97, by @melvincarvalho.

  • 16 June 2026

    Spec renders as raw source in browsers that block the cross-origin ReSpec script (self-host it) nostrcg/did-nostr#95, by @melvincarvalho.

  • 15 June 2026

    Optional derived Ed25519 verification method (same seed) for cross-ecosystem interop? nostrcg/did-nostr#94, by @melvincarvalho.

  • 15 June 2026

    Enhanced DID document uses `FollowsEndpoint`, `nip05`, `lud16`, `timestamp` — undefined in nostr/context (#68) nostrcg/did-nostr#93, by @melvincarvalho.

  • 15 June 2026

    `Multikey` is undefined under the declared `@context`: reference CID v1.0? (concrete case for #68) nostrcg/did-nostr#90, by @melvincarvalho.

• 20 issues closed.

  • 30 June 2026

    Publish as a W3C Community Group Draft Report (specStatus CG-DRAFT) — cut 0.1 nostrcg/did-nostr#134.

  • 30 June 2026

    Make the .well-known HTTP resolution path (incl. .json suffix) normative nostrcg/did-nostr#127.

  • 30 June 2026

    Standardize on relative verification-relationship references (#key1) across spec, vectors, implementations nostrcg/did-nostr#128.

  • 30 June 2026

    Reframe Update/Delete operations: document is mutable via the event layer; deactivation is an open item nostrcg/did-nostr#126.

  • 30 June 2026

    modified example value is off by 20 min (1737906600 = 15:50:00Z, not 15:30:00Z); also #relay vs #relay1 nostrcg/did-nostr#131.

  • 30 June 2026

    Thoughts and feedback nostrcg/did-nostr#1.

  • 30 June 2026

    Verify all specification terms are defined in vocabularies and contexts nostrcg/did-nostr#68.

  • 30 June 2026

    Enhanced DID document uses `FollowsEndpoint`, `nip05`, `lud16`, `timestamp` — undefined in nostr/context (#68) nostrcg/did-nostr#93.

  • 30 June 2026

    `FollowsEndpoint` is underspecified — mark at-risk and design the response format before publication nostrcg/did-nostr#104.

  • 30 June 2026

    Spec is unstyled in Brave: Brave blocks w3.org assets the server explicitly permits (optional: vendor CSS same-origin) nostrcg/did-nostr#97.

  • 30 June 2026

    add test vectors nostrcg/did-nostr#31.

  • 30 June 2026

    Document the resource model: subject vs document, httpRange-14, ETag/Last-Modified vs in-graph provenance (standalone explainer) nostrcg/did-nostr#123.

  • 30 June 2026

    Document the x-only vs Multikey parity model (0x02/0x03) as a standalone explainer (CG note / blog post) nostrcg/did-nostr#102.

  • 30 June 2026

    Deprecate `profile.timestamp` in favor of document-level `modified` nostrcg/did-nostr#117.

  • 30 June 2026

    `Nostr-Timestamp` header is redundant with `Last-Modified` — mark at-risk before publication nostrcg/did-nostr#103.

  • 30 June 2026

    Specify whether key transformation validates the identifier as a valid secp256k1 x-only key (x < p, on-curve) nostrcg/did-nostr#105.

  • 30 June 2026

    Design: provenance model (in-graph source-derived times + content-hash ETag + blocktrails), superseding `Nostr-Timestamp` nostrcg/did-nostr#106.

  • 16 June 2026

    Bump version to 0.0.11 nostrcg/did-nostr#98.

  • 16 June 2026

    `Multikey` is undefined under the declared `@context`: reference CID v1.0? (concrete case for #68) nostrcg/did-nostr#90.

  • 16 June 2026

    Spec renders as raw source in browsers that block the cross-origin ReSpec script (self-host it) nostrcg/did-nostr#95.

• 10 issues received 13 new comments.

  • Latest comment 30 June 2026

    Verify all specification terms are defined in vocabularies and contexts nostrcg/did-nostr#68 (2 comments by @melvincarvalho)

  • Latest comment 30 June 2026

    `FollowsEndpoint` is underspecified — mark at-risk and design the response format before publication nostrcg/did-nostr#104 (2 comments by @melvincarvalho)

  • Latest comment 30 June 2026

    Design: provenance model (in-graph source-derived times + content-hash ETag + blocktrails), superseding `Nostr-Timestamp` nostrcg/did-nostr#106 (2 comments by @melvincarvalho)

  • 30 June 2026

    DID Resolver: consolidate and improve implementation nostrcg/did-nostr#89 (1 comment by @melvincarvalho)

  • 30 June 2026

    Thoughts and feedback nostrcg/did-nostr#1 (1 comment by @melvincarvalho)

  • 30 June 2026

    Enhanced DID document uses `FollowsEndpoint`, `nip05`, `lud16`, `timestamp` — undefined in nostr/context (#68) nostrcg/did-nostr#93 (1 comment by @melvincarvalho)

  • 30 June 2026

    Spec is unstyled in Brave: Brave blocks w3.org assets the server explicitly permits (optional: vendor CSS same-origin) nostrcg/did-nostr#97 (1 comment by @melvincarvalho)

  • 30 June 2026

    add test vectors nostrcg/did-nostr#31 (1 comment by @melvincarvalho)

  • 30 June 2026

    `Nostr-Timestamp` header is redundant with `Last-Modified` — mark at-risk before publication nostrcg/did-nostr#103 (1 comment by @melvincarvalho)

  • 15 June 2026

    `Multikey` is undefined under the declared `@context`: reference CID v1.0? (concrete case for #68) nostrcg/did-nostr#90 (1 comment by @melvincarvalho)
• 17 pull requests opened.

  • 30 June 2026

    Publish as a Community Group Draft Report (specStatus CG-DRAFT) nostrcg/did-nostr#135, by @melvincarvalho.

  • 30 June 2026

    Pre-0.1 spec batch: normative .well-known, relative refs, Update/Delete reframe nostrcg/did-nostr#133, by @melvincarvalho.

  • 30 June 2026

    Fix modified example value (15:30 -> 15:50) + complete-vector relay id (#131) nostrcg/did-nostr#132, by @melvincarvalho.

  • 30 June 2026

    Use relative key references (#key1) in conformance vectors (#128) nostrcg/did-nostr#129, by @melvincarvalho.

  • 30 June 2026

    Remove FollowsEndpoint; defer large follow lists to relays + kind 3 (#104) nostrcg/did-nostr#125, by @melvincarvalho.

  • 30 June 2026

    Add resource model explainer note (#123) nostrcg/did-nostr#124, by @melvincarvalho.

  • 30 June 2026

    Bump version to 0.0.12 nostrcg/did-nostr#122, by @melvincarvalho.

  • 30 June 2026

    Add parity model explainer note (#102) nostrcg/did-nostr#121, by @melvincarvalho.

  • 30 June 2026

    Rename profile.timestamp to profile.created_at (#117) nostrcg/did-nostr#120, by @melvincarvalho.

  • 30 June 2026

    Specify identifier must be a valid secp256k1 x-only key (#105) nostrcg/did-nostr#119, by @melvincarvalho.

  • 30 June 2026

    Rewrite parity note as proper spec text (follow-up to #92) nostrcg/did-nostr#118, by @melvincarvalho.

  • 30 June 2026

    Add in-graph `modified` provenance field, drop `Nostr-Timestamp` header nostrcg/did-nostr#116, by @melvincarvalho.

  • 17 June 2026

    feat: Add comprehensive did:nostr v0.0.11 test vector suite and error-taxonomy conformance matrix nostrcg/did-nostr#101, by @amir-hameed-mir.

  • 16 June 2026

    Bump version to 0.0.11 nostrcg/did-nostr#99, by @melvincarvalho.

  • 16 June 2026

    Vendor ReSpec same-origin so the spec renders in browsers that block cross-origin scripts nostrcg/did-nostr#96, by @melvincarvalho.

  • 15 June 2026

    Document parity rationale (key tweaking) and Multikey provenance (#254) nostrcg/did-nostr#92, by @melvincarvalho.

  • 15 June 2026

    Use the CID v1.0 `@context` so `Multikey`/`publicKeyMultibase` are defined (#90) nostrcg/did-nostr#91, by @melvincarvalho.

• 17 pull requests merged.

  • 30 June 2026

    Publish as a Community Group Draft Report (specStatus CG-DRAFT) nostrcg/did-nostr#135.

  • 30 June 2026

    Pre-0.1 spec batch: normative .well-known, relative refs, Update/Delete reframe nostrcg/did-nostr#133.

  • 30 June 2026

    Fix modified example value (15:30 -> 15:50) + complete-vector relay id (#131) nostrcg/did-nostr#132.

  • 30 June 2026

    Use relative key references (#key1) in conformance vectors (#128) nostrcg/did-nostr#129.

  • 30 June 2026

    Remove FollowsEndpoint; defer large follow lists to relays + kind 3 (#104) nostrcg/did-nostr#125.

  • 30 June 2026

    Add resource model explainer note (#123) nostrcg/did-nostr#124.

  • 30 June 2026

    feat: Add comprehensive did:nostr v0.0.11 test vector suite and error-taxonomy conformance matrix nostrcg/did-nostr#101.

  • 30 June 2026

    Bump version to 0.0.12 nostrcg/did-nostr#122.

  • 30 June 2026

    Add parity model explainer note (#102) nostrcg/did-nostr#121.

  • 30 June 2026

    Rename profile.timestamp to profile.created_at (#117) nostrcg/did-nostr#120.

  • 30 June 2026

    Specify identifier must be a valid secp256k1 x-only key (#105) nostrcg/did-nostr#119.

  • 30 June 2026

    Rewrite parity note as proper spec text (follow-up to #92) nostrcg/did-nostr#118.

  • 30 June 2026

    Document parity rationale (key tweaking) and Multikey provenance (#254) nostrcg/did-nostr#92.

  • 30 June 2026

    Add in-graph `modified` provenance field, drop `Nostr-Timestamp` header nostrcg/did-nostr#116.

  • 16 June 2026

    Bump version to 0.0.11 nostrcg/did-nostr#99.

  • 16 June 2026

    Use the CID v1.0 `@context` so `Multikey`/`publicKeyMultibase` are defined (#90) nostrcg/did-nostr#91.

  • 16 June 2026

    Vendor ReSpec same-origin so the spec renders in browsers that block cross-origin scripts nostrcg/did-nostr#96.

• 6 pull requests received 29 new comments.

  • Latest comment 30 June 2026

    feat: Add comprehensive did:nostr v0.0.11 test vector suite and error-taxonomy conformance matrix nostrcg/did-nostr#101 (14 comments by @amir-hameed-mir, @melvincarvalho)

  • Latest comment 30 June 2026

    Pre-0.1 spec batch: normative .well-known, relative refs, Update/Delete reframe nostrcg/did-nostr#133 (7 comments by @melvincarvalho)

  • Latest comment 30 June 2026

    Publish as a Community Group Draft Report (specStatus CG-DRAFT) nostrcg/did-nostr#135 (3 comments by @melvincarvalho)

  • Latest comment 30 June 2026

    Use relative key references (#key1) in conformance vectors (#128) nostrcg/did-nostr#129 (2 comments by @amir-hameed-mir, @melvincarvalho)

  • Latest comment 30 June 2026

    Add in-graph `modified` provenance field, drop `Nostr-Timestamp` header nostrcg/did-nostr#116 (2 comments by @melvincarvalho)

  • 30 June 2026

    Rename profile.timestamp to profile.created_at (#117) nostrcg/did-nostr#120 (1 comment by @melvincarvalho)

nostrcg/schema

• 3 issues opened.

  • 30 June 2026

    Add `modified` term (dcterms:modified) to the context nostrcg/schema#23, by @melvincarvalho.

  • 29 June 2026

    Versioning: package.json is stale and the ontology carries no version metadata nostrcg/schema#21, by @melvincarvalho.

  • 29 June 2026

    Add lightweight discovery predicate: map seeAlso → rdfs:seeAlso in the context nostrcg/schema#19, by @melvincarvalho.

• 2 issues closed.

  • 30 June 2026

    Add `modified` term (dcterms:modified) to the context nostrcg/schema#23.

  • 29 June 2026

    Add lightweight discovery predicate: map seeAlso → rdfs:seeAlso in the context nostrcg/schema#19.

• 5 pull requests opened.

  • 30 June 2026

    Bump version to 0.0.19 nostrcg/schema#25, by @melvincarvalho.

  • 30 June 2026

    Add `modified` term (dcterms:modified) to context nostrcg/schema#24, by @melvincarvalho.

  • 29 June 2026

    Bump version to 0.0.18 nostrcg/schema#22, by @melvincarvalho.

  • 29 June 2026

    Add seeAlso term (rdfs:seeAlso) to context for resource discovery nostrcg/schema#20, by @melvincarvalho.

  • 19 June 2026

    Define `nip05` and `lud16` profile terms nostrcg/schema#18, by @melvincarvalho.

• 5 pull requests merged.

  • 30 June 2026

    Bump version to 0.0.19 nostrcg/schema#25.

  • 30 June 2026

    Add `modified` term (dcterms:modified) to context nostrcg/schema#24.

  • 29 June 2026

    Bump version to 0.0.18 nostrcg/schema#22.

  • 29 June 2026

    Add seeAlso term (rdfs:seeAlso) to context for resource discovery nostrcg/schema#20.

  • 19 June 2026

    Define `nip05` and `lud16` profile terms nostrcg/schema#18.

• 1 pull request received 1 new comment.

  • 29 June 2026

    Add seeAlso term (rdfs:seeAlso) to context for resource discovery nostrcg/schema#20 (1 comment by @melvincarvalho)