10/11
This was a problem because it was not the desired behavior for Bitcoin TXs.
In some cases could have led to network splits.
Plus, could allow for some attacks, where you can reduce the confirmation of a TX to 1, making it more susceptible to double-spending.
(could****)
raw_avocado / Alex Waltz
npub1pu…6pn0a
2024-01-10 19:11:12
in reply to nevent1q…pfg7
Author Public Key
npub1pu5pjm8dzqjtul8t84a3jsehh78jreadp297sqa3as98c5hfym0qu6pn0aPublished at
2024-01-10 19:11:12Event JSON
{
"id": "4c5e3974e523c4baf55b70cfe0ec685bb44b21f3a54578be4d780b699cb655fd",
"pubkey": "0f28196ced1024be7ceb3d7b194337bf8f21e7ad0a8be803b1ec0a7c52e926de",
"created_at": 1704913872,
"kind": 1,
"tags": [
[
"e",
"69f7c9372b4a6a3b3bd50fc51e8ef1a3813548ccae62b753aba8e3ffec91015b",
"",
"root"
],
[
"e",
"b5e39b8f2edfe57094ab8138f87e55f1c0c6f572ab1f5ac2ea6f4396ae014b34",
"",
"reply"
],
[
"p",
"0f28196ced1024be7ceb3d7b194337bf8f21e7ad0a8be803b1ec0a7c52e926de"
]
],
"content": "10/11\nThis was a problem because it was not the desired behavior for Bitcoin TXs.\n\nIn some cases could have led to network splits.\n\nPlus, could allow for some attacks, where you can reduce the confirmation of a TX to 1, making it more susceptible to double-spending.\n(could****)",
"sig": "5935d413aa510b04ca8ae4a6eb20f56ae17dec7fbeb5f41d134372daf217c0f44df7ca285f4f0102dd9f34fc5e4e5dd62a47e012d15fba24bab5bf9d90aa25f1"
}