📅 Original date posted:2022-10-27
📝 Original message:More generally, some of the arguments against full RBF seem like debatable
reasons (though not fully convincing) to possibly leave it off, and/or
disabled by default, but definitely NOT reasons to remove the option and
prevent users from deciding for themselves.
On Thursday 27 October 2022 15:37:27 Anthony Towns via bitcoin-dev wrote:
> "Can I prevent someone else's transaction from propagating" is almost
> the entirety of the question with -datacarrier, -datacarriersize and
> -permitbaremultisig though:
Not necessarily the entirety, no. Even if others would propagate it, you also
don't want to waste _your_ bandwidth doing so. This also reveals a difference
between the two policies: with RBF, you have _already_ spent resources
propagating the first transaction (what this implies is not immediately
obvious).
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 23:15:56
in reply to nevent1q…xgy6
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 23:15:56Event JSON
{
"id": "0f028e3cecda80e5d8d2ad67cdaa83ae85dd6f078870c706d03a451c380bcdb2",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686179756,
"kind": 1,
"tags": [
[
"e",
"72e405df3aaafafab176501cba9ee9ab7db3f9a3f761dd313e13dd7ef49c1f95",
"",
"root"
],
[
"e",
"4aed3ea65726ec7c3dd8ee422422194d5921f505a2b1299ad74157943a32b630",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2022-10-27\n📝 Original message:More generally, some of the arguments against full RBF seem like debatable \nreasons (though not fully convincing) to possibly leave it off, and/or \ndisabled by default, but definitely NOT reasons to remove the option and \nprevent users from deciding for themselves.\n\nOn Thursday 27 October 2022 15:37:27 Anthony Towns via bitcoin-dev wrote:\n\u003e \"Can I prevent someone else's transaction from propagating\" is almost\n\u003e the entirety of the question with -datacarrier, -datacarriersize and\n\u003e -permitbaremultisig though:\n\nNot necessarily the entirety, no. Even if others would propagate it, you also \ndon't want to waste _your_ bandwidth doing so. This also reveals a difference \nbetween the two policies: with RBF, you have _already_ spent resources \npropagating the first transaction (what this implies is not immediately \nobvious).\n\nLuke",
"sig": "ae9a1062d984f41f7f6d505f89fa1c6412aff890250e2b90a14c6be6443ecb2cab8d6ba0035e99ce3feeee662877ccd19892591401681bf3a9d2a9ed9297f60f"
}