Treat kind 0 (profiles) as replaceable per NIP-01#72
Merged
alejandro-runner merged 1 commit intomainfrom Feb 3, 2026
Merged
Conversation
- Deduplicate kind 0 in-memory by pubkey, keep latest by created_at - Add findExistingKind0Event() to look up current profile in DynamoDB - In shouldStoreEvent, replace existing kind 0 when newer event arrives - Extract buildEventMap to dedup.ts for testability; add unit tests Closes #68 Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Nostr kind 0 (metadata) is replaceable: only the latest event per pubkey should be kept. The Lambda previously deduplicated kind 0 by event id, so every profile update was stored and
search_food_establishmentsreturned duplicate entries (e.g. multiple "El Candado" with the same@id).Changes
0:${event.pubkey}; the event with the latestcreated_atis kept.created_at(or null).event.kind === 0: if an existing kind 0 exists, store only if the new event is newer and returnoldEventIdso the store loop can delete the previous row.dedup.tsand used inqueryNostrRelays; unit tests added indedup.test.ts.Lambda tests:
cd lambda/nostr-querier && npm test(3 tests for kind 0 and general dedup).Closes #68