aboutsummaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorMatt Corallo <git@bluematt.me>2017-08-24 11:36:07 -0400
committerMatt Corallo <git@bluematt.me>2017-09-11 15:51:25 -0400
commitba206d2c63a8d3cbd4a8dd47e9ef126af1bb3bb9 (patch)
treeae365cb374d581224b5fee69629e4f235f0d71f4 /test
parent31e72b284ef54c4c221015c8d700946c6143fb7a (diff)
downloadbitcoin-ba206d2c63a8d3cbd4a8dd47e9ef126af1bb3bb9.tar.xz
Deprecate confusing blockmaxsize, fix getmininginfo output
* This removes block-size-limiting code in favor of GBT clients doing the limiting themselves (if at all). * -blockmaxsize is deprecated and only used to calculate an implied blockmaxweight, addressing confusion from multiple users. * getmininginfo's currentblocksize return value was returning garbage values, and has been removed, also removing a GetSerializeSize call in some block generation inner loops and potentially addressing some performance edge cases.
Diffstat (limited to 'test')
-rwxr-xr-xtest/functional/mining.py1
1 files changed, 0 insertions, 1 deletions
diff --git a/test/functional/mining.py b/test/functional/mining.py
index 93f9838896..c8fb1062b7 100755
--- a/test/functional/mining.py
+++ b/test/functional/mining.py
@@ -38,7 +38,6 @@ class MiningTest(BitcoinTestFramework):
mining_info = node.getmininginfo()
assert_equal(mining_info['blocks'], 200)
assert_equal(mining_info['chain'], 'regtest')
- assert_equal(mining_info['currentblocksize'], 0)
assert_equal(mining_info['currentblocktx'], 0)
assert_equal(mining_info['currentblockweight'], 0)
assert_equal(mining_info['difficulty'], Decimal('4.656542373906925E-10'))