This is habla: https://habla.news/a/naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx
This is NostrBounty:
Look at the naddr1 in the url. I think Habla is addressing it correctly and NostrBounty is either wrong or has a new post, with a new id, for it. But I cannot find this new post anywhere.
I need to decode the bech32 now. Why is there no online decoder yet? Should I launch a bounty or is there one?
I suspect these reference the same post but using some slightly different semantics. Does nostr have a malleability issue?
It shouldn't, the naddr spec is very clear. If they are the same, they must have the same naddr. They definitely have different d tags. But I cannot find the original NostrBounty JSON to be sure. If so, then they are two separate events.
```
> nip19.decode('naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx')
{
type: 'naddr',
data: {
identifier: '1679509418',
pubkey: '46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d',
kind: 30023,
relays: []
}
}
> nip19.decode('naddr1qpqrwve3v56nxv3cxv6nvdeex9jrzctyvdskgcnyvcck2ce5xcekydrpvvungvf4v33njwfkvcmnjcf4vvmn2vrpxqenscnxxe3rwef4xgpzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqvzqqqr4gukgahaj')
{
type: 'naddr',
data: {
identifier: '731e5328356791d1adcadbdf1ec463b4ac9415dc996f79a5c750a038bf6b7e52',
pubkey: '46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d',
kind: 30023,
relays: []
}
}
```
weird.
It's likely two different posts, the latter has an derived identifier from the post itself while the first one has a custom identifier (which should be d-tag in the event). Some clients posts to Relays that doesn't implement NIP-33 and that can cause some issues.
No, it's just a bug in the code: https://github.com/diamsa/nostrbounties/issues/2
