Event JSON
{
"id": "ddd34ba697a0f43a0038de6e963d52f0f38b917eebf4c3c9e78ed04ceb4a6339",
"pubkey": "fcf6fee0e959c7195dadc5f36fe5a873003b389e7033293b06057c821fcbc9c5",
"created_at": 1677160226,
"kind": 1,
"tags": [
[
"e",
"70147bdeea1e2ec693be95fd2562e1fb9a5411e0b26b5820ec4bf40815564321",
"",
"root"
],
[
"e",
"980f969575a44f6f2ae00b3b76a827ab75e36097dbacb23880d9a274e8912d62",
"",
"reply"
],
[
"p",
"fcf6fee0e959c7195dadc5f36fe5a873003b389e7033293b06057c821fcbc9c5"
]
],
"content": "This also made me think of an active discussion in the Bitcoin-Dev mailing list regarding an attack vector on multiparty protocols (such as Lightning or coinjoins, and even more opening Lightning channels in coinjoins) using Taproot inputs, \n\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021444.html\n",
"sig": "ac45afb4f29193ddf8a5395f8743ecedf229ebc6a07763cf79f5552b625a170b79a863a04eb72d5a8c309b85d8a055318ffb2eab51c1660aa56c42294fe8e3c9"
}