CreateTransaction: suggest/enforce fee for big low-priority transactions to avoid backlog #86

issue molecular openend this issue on March 1, 2011
  1. molecular commented at 2:54 am on March 1, 2011: none

    currently (2011/03/01) a backlog of transactions that dont seem make it into blocks is building up (according to ArtForz now 670 transactions).

    People are starting to complain, see http://www.bitcoin.org/smf/index.php?topic=3835.msg57031#msg57031 for an example.

    This was discussed on #bitcoin-dev

    ArtForz> that tx should have a score of 20567855 ArtForz> so it falls short of the dPriority > COIN * 144 / 250 test ArtForz> and as tx size is > 4000, fAllowFree is never true for it theymos> Ah. So it will never confirm? ArtForz> probably not

    ArtForz> looks like the tx-sending code needs some fixing molecular> like not generate a tx with a score too low, or suggest to add a fee? ArtForz> yep ArtForz> check size and priority of transaction, if it’s > 4kB and score < 57600000 require min fee ArtForz> maybe reduce the size limit to 3.5k or so, otherwise it can only get into an otherwise empty block

    This also seems to imply the possiblity of a DoS-Attack on node RAM, since the tx-queue is kept im RAM. Maybe the transaction cache should not be unlimited?

  2. gasteve commented at 3:11 am on March 1, 2011: none
    Is there another potential issue here? For transactions that, for one reason or another, don’t get into a block in a reasonable amount of time, is there some criteria for which the network will drop (and thereby cancel) such transactions? (like a certain amount of time passing without being included in a block)
  3. molecular commented at 2:16 pm on March 1, 2011: none

    afaik, there is currently no mechanism that would drop transactions from local cache. They just stay there until found in a block.

    It’s been suggested to do that, though (like limit local cache to 5MB), in order to avoid DoS attack. It’s probably not that simple, though.

    Don’t know if there’s a github issue for this, if not, it certainly deserves one.

  4. gavinandresen commented at 3:40 pm on March 1, 2011: contributor
  5. jgarzik commented at 3:17 am on March 3, 2011: contributor
    See pull request at #88
  6. nelisky referenced this in commit ea24796726 on Dec 5, 2013
  7. dexX7 referenced this in commit e2bca96e57 on Jun 22, 2015
  8. classesjack referenced this in commit 306754dad8 on Jan 2, 2018
  9. 8bitcoder referenced this in commit 94c1ae46b9 on Jan 30, 2018
  10. CryptAxe referenced this in commit 1771776bd9 on Mar 6, 2018
  11. attilaaf referenced this in commit 4e569dff24 on Sep 20, 2019
  12. Losangelosgenetics referenced this in commit a25c06d5b1 on Mar 12, 2020
  13. rajarshimaitra referenced this in commit 3ce10cc84e on Aug 5, 2021
  14. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-10-30 00:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me