You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Multiple tags are being selected for Dedup keys for Addressable evnets/Parametrized replacable events #478
Describe the bug
For "addressable events" (formerly called parameterized replacable events), for extracting dedup keys for metadata of the events, multiple tags are being selected.
For Example:
For events with tags [d, "hello", "ball"]
current implementation takes ["hello", "ball"].
Expected behavior
Accoridng to NIP specs, dedup key should be:
["hello"].
Screenshots
N/A
System (please complete the following information):
General
Logs
N/A
Files to see
The bugged implementation logic is in parametrized-replacable-events-strategy.ts at const [, ...deduplication] = event.tags.find((tag) => tag.length >= 2 && tag[0] === EventTags.Deduplication) ?? [null, '']
Additional context
This might result in unexpected behavior as now the event row may not be replaced.
Activity
fix: NIP-01 compliance - use only first value for parametrized replac…
cameri commentedon Apr 19, 2026
Thank you @kushagra0902 !
fix: NIP-01 compliance - use only first value for parametrized replac…