From 45bb7742bf4a7f8312eb57150496c2408121c040 Mon Sep 17 00:00:00 2001 From: Melvin Carvalho Date: Tue, 30 Jun 2026 15:35:30 +0200 Subject: [PATCH] Bump version to 0.0.2 DID-document output now conforms to did:nostr 0.0.12 (#39): - profile.timestamp -> profile.created_at (the kind-0 created_at; now a defined context term, nostr:created_at). - Emit "modified" (dcterms:modified, ISO-8601) = max(created_at) over the signed parts actually composed into the document (kind 0 / 3 / 10002). Minimal docs carry none. - Bound inlined follows to a subset (500), short-circuited; the complete signed list is the kind-3 event on the relays (no FollowsEndpoint). - Hardened the public resolver path: corrupt/out-of-range created_at no longer throws (returns no modified), Number.isSafeInteger throughout, and a kind-0 that only contributes alsoKnownAs no longer emits a bare {created_at} profile yet still counts toward modified. Refs: nostrcg/did-nostr 0.0.12 (#106 modified, #117 created_at, #104/#125 follows). --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 4d82d92..e869cc2 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "beacon", - "version": "0.0.1", + "version": "0.0.2", "type": "module", "description": "did:nostr social-graph indexer (profiles + follows + relay lists) on MongoDB. Same schema as nostr-beacon for regression; DID-doc generation delegates to jss buildDidDocument per RFC.", "bin": {