Event JSON
{
"id": "d0fcb6d5a8c78ccddfa75e028b5cbba3cf2a121d2cb59bb39d5801433247acb8",
"pubkey": "0326b57e042e0892839adc73784689d485bffd285a1dccfe9c5adada479a1d4c",
"created_at": 1749490626,
"kind": 1,
"tags": [
[
"p",
"0326b57e042e0892839adc73784689d485bffd285a1dccfe9c5adada479a1d4c",
"",
"mention"
],
[
"p",
"b133bfc57bed61c391d4e8f953b906c7f1709c438d91c75fb6daf79449d5789d",
"",
"mention"
],
[
"p",
"70441609369d77ea553d805ee9af58b29e4c39d5b08b3956741839c2f3feebcc",
"",
"mention"
],
[
"e",
"0f4188831cbea8ebb275af7b5b2fdd85d2534ad632d70f735ee9a26567b5a905",
"",
"root"
],
[
"e",
"592f9edf21d4b88fdf72d7434f3586fe6a13d6bf12beecc35f37886b239ce728",
"",
"reply"
]
],
"content": "Do you think the community will just wait it out for fcmp++ or does the delay justify a hard fork sooner for improving ring signatures like mentioned in the ospead report, before fcmp++ gets implemented?",
"sig": "a02efa032d84739abc40d0a4fcb7ea080c1e73e57b1676d92156cfbc66323fd5fed07c708bd6a5a71dda26a790a8da13afc654472336af071c5479075dbd16de"
}
