📅 Original date posted:2015-07-09 📝 Original message:Replace-by-anything can ...

Tom Harding [ARCHIVE] /

npub1mse…mwjy

2023-06-07 15:41:49

in reply to nevent1q…p60h

📅 Original date posted:2015-07-09
📝 Original message:Replace-by-anything can only work if conflicts are relayed, so the
solution is not to act against the peer.

Alex Morcos offered a suggestion on IRC -- track recently-rejected
txid's and don't getdata them. The idea sounds good to me.

On 7/9/2015 4:55 PM, Matt Whitlock 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Author Public Key

npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjy

Show more details

Published at

2023-06-07 15:41:49

Kind type

1 Short Text Note

Event JSON

{ "id": "7b36734b5e5224481e8b51c5cd55b5ac447062e5ec7c1e4aa830ac24ce0453a1", "pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3", "created_at": 1686152509, "kind": 1, "tags": [ [ "e", "b3856dc84fad9e3da113cb809110ffcebdf01e349fe2ffc93e81d06232da1b52", "", "root" ], [ "e", "d84a5f171d48e2209bf44a25f1006545559c249fc2fb0ecaf9d3168f0b3d7b9d", "", "reply" ], [ "p", "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91" ] ], "content": "📅 Original date posted:2015-07-09\n📝 Original message:Replace-by-anything can only work if conflicts are relayed, so the\nsolution is not to act against the peer.\n\nAlex Morcos offered a suggestion on IRC -- track recently-rejected\ntxid's and don't getdata them. The idea sounds good to me.\n\n\nOn 7/9/2015 4:55 PM, Matt Whitlock wrote:\n\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\n\u003e [1] https://github.com/petertodd/bitcoin/commits/replace-by-fee-v0.10.2\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev", "sig": "3ebe839b03849087834b390049ee4390ffa5853883f013a9fbae17a95f175de4b24c554a7953682cb0182bcf47b6bc2b1b3433ccfdbb6758b6a38c7da1c072df" }