Nostr Web Client

here's a game of spot the difference:

haha, just kidding, they are identical as you would see if you put one over the other and made them transparent

according to my json canonical formatting function, the ID they have is actually wrong, which means the signature is invalid, and my relay refuses to save it

someone, who i can't find fcd720c38d9ee337188f47aac845dcd8f590ccdb4a928b76dde18187b4c9d37d nostr:npub1lntjpsudnm3nwxy0g74vs3wumr6epnxmf2fgkakauxqc0dxf6d7smau8ar which i guess is an anonymous zap, the client is not doing the canonical version correctly and thus getting wrong data

looks like it's a bug in mutiny wallet

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

also, my ID derivation function is 100% functional, it only complains for events that have nonstandard escapes in them, the second image above is what it gets when it unmarshals and marshals back

the actual raw output the fields are in different order but the canonical form does not have this difference

this particular event type, the zap, i see now and then bogus ones, probably because it has json embedded inside the content field, and this is a thing that leads to problems with varying compliance of the json functions in the relays (and clients) to the actual NIP-01 spec for deriving IDs

when i feed the relay a shit-ton of events like what i got from nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj, i would estimate that about 1-2% of all events it has are not nip-01 compliant but clearly whatever relay semisol uses (strfry, i guess) must not actually refuse to store events with unverifiable signatures

when the signature field is wrong, the event should be rejected and the client developer should get a paddling

Moel 1y ago

Did you report this bug with the nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg people ?

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i guess you just did, i wasn't following them so my client wasn't grabbing the npub

it's impossible to know what their code is doing wrong without seeing the canonical event array form they are generating, my best guess is it's something to do with json string escaping though, that's almost consistently been the problem for me in the past