Asone on Nostr: I know the event hash is a sha256 of the serialized event, however in above example, ...
I know the event hash is a sha256 of the serialized event, however in above example, relay C would obviously compute the hash from original event before storing a modified version of the content but with the original hash.
Do clients already performs checks onto the received events to ensure the content is legit ?
Published at
2023-11-07 07:40:05Event JSON
{
"id": "5afeaaa83b63e5793cdec29e3bcce1aa6ff15e4231e26f0413b7e9c4230af56d",
"pubkey": "7a5af9e01b137408e7cb2d85fb9d5d8395297ac19faf266069b82bc20b156859",
"created_at": 1699342805,
"kind": 1,
"tags": [
[
"e",
"fe03cff8b4e35eef5fdaaec354d176cfceb2f7537ac3c87d93ec5d69e9ae873c",
"",
"root"
],
[
"p",
"7a5af9e01b137408e7cb2d85fb9d5d8395297ac19faf266069b82bc20b156859"
]
],
"content": "I know the event hash is a sha256 of the serialized event, however in above example, relay C would obviously compute the hash from original event before storing a modified version of the content but with the original hash. \n\nDo clients already performs checks onto the received events to ensure the content is legit ?",
"sig": "e08d756858198baecae418bcb9ddb0bc5f8fab484e8cd3293bc748c11af9e2c9f3fd5b8783ca6ab8e04d89bc60eadf48950988288e8b2a86a975c778e207e1b8"
}
