📅 Original date posted:2015-07-09
📝 Original message:Um, it's called "replace-by-fee" for a reason. The transaction [set] paying the highest fee [rate] is always the one that will be accepted. You can't use the order in which transactions were received to determine which one is the "replacing" transaction and which is/are the "replaced" transaction(s) because order is not defined for transactions in the mempool. (Ordering transactions is precisely why we must have a block chain.)
On Thursday, 9 July 2015, at 5:42 pm, Raystonn wrote:
> It is a mistake for RBF to assume a transaction with lower fee is invalid. If I paid a higher fee to get a one hour confirmation in the current congestion, I might want to drop back to a lower fee if I see the spam stop.
>
> On 9 Jul 2015 4:55 pm, Matt Whitlock <bip at mattwhitlock.name> wrote:
> > I'm presently running my full node with Peter Todd's full replace-by-fee patch set [1]. I am seeing a LOT of messages in the log about replacement transactions being rejected due to their paying less in fees than the transactions they would replace. I understand that this could happen legitimately from time to time, due to my node's receiving a replacing transaction prior to receiving the replaced transaction; however, due to the ongoing spam attack, I am seeing a steady stream of these rejection messages, dozens per second at times. I am wondering if each replacement rejection ought to penalize the peer who relayed the offending transaction, and if the penalty builds up enough, then the peer could be temporarily banned, similar to how other "misbehaving" peers are treated.
> >
> > [1] https://github.com/petertodd/bitcoin/commits/replace-by-fee-v0.10.2
Matt Whitlock [ARCHIVE] /
npub17q…upwet
2023-06-07 15:41:49
in reply to nevent1q…cr9u
Author Public Key
npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwetSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:41:49Event JSON
{
"id": "23d161b75b74332aa2aef271bb56eaa4f5febd7fe17af9f0666e263b5d8ba74d",
"pubkey": "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91",
"created_at": 1686152509,
"kind": 1,
"tags": [
[
"e",
"b3856dc84fad9e3da113cb809110ffcebdf01e349fe2ffc93e81d06232da1b52",
"",
"root"
],
[
"e",
"1212287e813dbcf823178d8962e09ffb181b52a744805a3ef918d38c1c8922d2",
"",
"reply"
],
[
"p",
"fbac73d2413d23d5b6e60bc431152069981e56a94cd5d626c9e88b6c0a18cbd5"
]
],
"content": "📅 Original date posted:2015-07-09\n📝 Original message:Um, it's called \"replace-by-fee\" for a reason. The transaction [set] paying the highest fee [rate] is always the one that will be accepted. You can't use the order in which transactions were received to determine which one is the \"replacing\" transaction and which is/are the \"replaced\" transaction(s) because order is not defined for transactions in the mempool. (Ordering transactions is precisely why we must have a block chain.)\n\n\nOn Thursday, 9 July 2015, at 5:42 pm, Raystonn wrote:\n\u003e It is a mistake for RBF to assume a transaction with lower fee is invalid. If I paid a higher fee to get a one hour confirmation in the current congestion, I might want to drop back to a lower fee if I see the spam stop.\n\u003e \n\u003e On 9 Jul 2015 4:55 pm, Matt Whitlock \u003cbip at mattwhitlock.name\u003e wrote:\n\u003e \u003e I'm presently running my full node with Peter Todd's full replace-by-fee patch set [1]. I am seeing a LOT of messages in the log about replacement transactions being rejected due to their paying less in fees than the transactions they would replace. I understand that this could happen legitimately from time to time, due to my node's receiving a replacing transaction prior to receiving the replaced transaction; however, due to the ongoing spam attack, I am seeing a steady stream of these rejection messages, dozens per second at times. I am wondering if each replacement rejection ought to penalize the peer who relayed the offending transaction, and if the penalty builds up enough, then the peer could be temporarily banned, similar to how other \"misbehaving\" peers are treated.\n\u003e \u003e \n\u003e \u003e [1] https://github.com/petertodd/bitcoin/commits/replace-by-fee-v0.10.2",
"sig": "7e6ea62330756462e5ffbc6dd33da4b4479be3c4caa71f49566f6e302c024d38bb7eb82ec7b73e7e0c519b4da7dcfd252b4be717c6a701dae4104d1c9539c79b"
}