Interesting... I am unable to verify that the event id of the quoted event matches the hash of the content.
Does it match for you? In native Kotlin, the sha256 of the content is not the id.
The signature checks if you use the event id, but it doesn't if i try to hash it again.
That's why Amethyst doesnt display. It doesn't accept as a valid message.
Login to reply
Replies (7)
id matches for me
Something is off .. have to remove the two special chars in the message to match the id. Are we supposed to remove nonutf8 chars?
You certainly should not, and if the spec works that way, the spec is wrong. Don't display anything that isn't hashed or otherwise verified.
Some weird String to ByteArray differences going on... Looks like Nostr follows whatever JavaScript is doing.
Nostr's underlying serialization format is a really stupid thing to use for a cryptographic system. I won't be surprised if this has something to do with the bug.
d41733136b81288fbd161707e080c5adc42195312a2bab32100f16e43a3e01c9