Event JSON
{
"id": "fb39c0c42f6bd4f85229e5a929bd83559b4816c94379f3eb6889228df13e2f89",
"pubkey": "00000001505e7e48927046e9bbaa728b1f3b511227e2200c578d6e6bb0c77eb9",
"created_at": 1741404066,
"kind": 1,
"tags": [
[
"e",
"8f9970d3a5262b96858d3125e7dbe4b1dfff70ac9cc28642bd497ae3f0f1175d",
"",
"root"
],
[
"e",
"000001c0d15df79e2ffc954c8b1313cbed28f88e5a43f6cd91500c41bba3a8c8"
],
[
"e",
"c3f85bdcf7ad3e50d9c659052dccdf46967f722f9e266ab101f6e832475303fb",
"",
"reply"
],
[
"p",
"7776c32d4b1d1e8bf2a96babeb43ad9ade157bd363d89b87fb63e6f145558888"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"7776c32d4b1d1e8bf2a96babeb43ad9ade157bd363d89b87fb63e6f145558888"
],
[
"r",
"https://nips.4rs.nl/nips/13/"
]
],
"content": "You actually can't, because the event can be broadcast any time, the clients should update the `created_at` when mining a note. You should file an issue for who doesn't.\n\n\u003e It is recommended to update the created_at as well during this process.\nhttps://nips.4rs.nl/nips/13/",
"sig": "75ae891e6c83d638cc107e22a78439318088b28c9611e6caed413ba4bbbf3a276d14d2f5ec2cbe4819b5d1947665291a4ec0cf1de6f24b3cb9bad0dbca57136f"
}