Sep 18 2019
Feb 15 2019
Feb 14 2019
Nov 18 2018
Sep 27 2018
Sep 12 2018
May 25 2018
src/test/buildenv.py has been generated by an old in-tree build from late 2017, it is not used anymore. sorry for the noise.
May 24 2018
internal branch reorg. no code changes
remove a spurios commit
last change wasn't supposed to update this diff.. fixing
diff seems sensible even if automatic build fails (https://reviews.bitcoinabc.org/harbormaster/build/3370/), it seems more an infrastructure problem rather than a code problem
Squash local commits
Dunno why but for some reason I seem to have added src/test/buildenv.py by error, wonder if we could add it to .gitignore
Apr 9 2018
nothing wrong with the diff, but wasn't secp256k1 handled as a subtree? is this changed since @tomtomtom7's utxo commitments patches?
Mar 1 2018
Jan 24 2018
Jan 17 2018
Jan 15 2018
patch is still WIP right? cause I don't see any criteria on how to apply excessUTXOCharge
Jan 9 2018
superseded by D866
Jan 2 2018
On second thought I think I will setup a new unit test to see if minrelayfee could be set to 0 and leave the more complete functional test on D554.
Test you referring to is part of D554 as this change was.
rebased on top of master and D856
Jan 1 2018
- just wanted to further specify that minrelaytxfee will be overruled once the mempool will get full and mempol accpetance fee will be modified via incrementalrelay
Dec 31 2017
Dec 29 2017
I partly agree, but we have to take into consideration that theoretically it is not possible to relay more than 20KB of free transactions per minute. Hence 200KB worth of free transactions per block.
Dec 27 2017
- modify sendrawtransaction (in src/rpc/rawtransaction.cpp) so that locally generated transaction is rate limited accordinf to limiterfreerelay
Change default for key fee transactions policies
Dec 15 2017
- Add unit test to verify that 0 fee non high priority transactions are selected for inclusion in a block.
- let minrelaytxfee to be set to 0.
Dec 11 2017
These set of changes fixed a runtime error occuring during the execution of miner_tests.
It was due to the use of ForceSetArg in TestPackageSelection to change the default value of blockMinFeeRate.
Dec 7 2017
Add comment to explain what DEFAULT_LIMITFREERELAY is
Oct 30 2017
Sep 30 2017
Guess that a link to the email where the algo is described should be put somewhere in the code comment or in the commit message
Sep 28 2017
Sep 27 2017
wonder if you could have used git subtree rather than including the code directly in the ABC tree
did't mean to accept to for the all abc project, forgot to untick the check button.
Sep 22 2017
Add WIP to title a list of TODO taks
Sep 21 2017
100% agreed on having an a Task where to discuss about how to reload bitcoin.conf, be it via a RPC command reload_config or via a SIGHUP sent to bitcoind.
I guess that we need to weight if the added complexity justify the addition of the RPC command.
Run high_priority_transaction.py 240 times in a loop and didn't experience any failure. Previously I got around 7-10% failure ratio.
testing now report back later.