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