Did you report this bug with the nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg people ?
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
Discussion
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