monzero-core.git/tests/unit_tests/hardfork.cpp, branch v0.14.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.14.0.12019-02-12T12:15:54ZArticMine's new block weight algorithm2019-02-12T12:15:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-01-21T17:18:50Zurn:sha1:ebc60a098d40506fdd0c5974a8644728d502e024
This curbs runaway growth while still allowing substantial
spikes in block weight
Original specification from ArticMine:
here is the scaling proposal
Define: LongTermBlockWeight
Before fork:
LongTermBlockWeight = BlockWeight
At or after fork:
LongTermBlockWeight = min(BlockWeight, 1.4*LongTermEffectiveMedianBlockWeight)
Note: To avoid possible consensus issues over rounding the LongTermBlockWeight for a given block should be calculated to the nearest byte, and stored as a integer in the block itself. The stored LongTermBlockWeight is then used for future calculations of the LongTermEffectiveMedianBlockWeight and not recalculated each time.
Define: LongTermEffectiveMedianBlockWeight
LongTermEffectiveMedianBlockWeight = max(300000, MedianOverPrevious100000Blocks(LongTermBlockWeight))
Change Definition of EffectiveMedianBlockWeight
From (current definition)
EffectiveMedianBlockWeight = max(300000, MedianOverPrevious100Blocks(BlockWeight))
To (proposed definition)
EffectiveMedianBlockWeight = min(max(300000, MedianOverPrevious100Blocks(BlockWeight)), 50*LongTermEffectiveMedianBlockWeight)
Notes:
1) There are no other changes to the existing penalty formula, median calculation, fees etc.
2) There is the requirement to store the LongTermBlockWeight of a block unencrypted in the block itself. This is to avoid possible consensus issues over rounding and also to prevent the calculations from becoming unwieldy as we move away from the fork.
3) When the EffectiveMedianBlockWeight cap is reached it is still possible to mine blocks up to 2x the EffectiveMedianBlockWeight by paying the corresponding penalty.
v8: per byte fee, pad bulletproofs, fixed 11 ring size2018-09-11T13:38:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-18T21:24:53Zurn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735blockchain_db: remove unused get_output_key variant2018-07-30T21:57:47Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-30T21:27:33Zurn:sha1:43f71100bc3e52d06061ef24ba13aa238c01a1f3
It was actually incorrect, as it would not return commitment
Merge pull request #40132018-07-19T18:40:42Zluigi1111luigi1111w@gmail.com2018-07-19T18:40:42Zurn:sha1:3e026ff6edbdf9e6c300ac737c4cccfaeafb0516
e5592c4 rpc: add blockchain disk size to getinfo (moneromooo-monero)
Merge pull request #39812018-07-19T18:39:24Zluigi1111luigi1111w@gmail.com2018-07-19T18:39:24Zurn:sha1:21afa71ba6d2f4e5e07dd91b69b2950820493a2c
45e419b db: store cumulative rct output distribution in the db for speed (moneromooo-monero)
Merge pull request #38542018-07-19T18:35:25Zluigi1111luigi1111w@gmail.com2018-07-19T18:35:25Zurn:sha1:025187e6c9206fc970b66f7459919ce0131fc612
149da42 db_lmdb: enable batch transactions by default (stoffu)
34cb6b4 add --regtest and --fixed-difficulty for regression testing (vicsn)
9e1403e update get_info RPC and bump RPC version (vicsn)
207b66e first new functional tests (vicsn)
db: store cumulative rct output distribution in the db for speed2018-07-13T10:37:04Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-05-22T13:46:30Zurn:sha1:45e419bd5c756337635feccec388efedf04f44ac
This gets rid of the temporary precalc cache.
Also make the RPC able to send data back in binary or JSON,
since there can be a lot of data
This bumps the LMDB database format to v3, with migration.
add --regtest and --fixed-difficulty for regression testing2018-06-29T08:06:11Zvictorsintnicolaasvicsn@users.noreply.github.com2018-06-14T19:11:49Zurn:sha1:34cb6b4b703f30be89388f4cdcc5d7b6780ee988
on_generateblocks RPC call combines functionality from the on_getblocktemplate and on_submitblock RPC calls to allow rapid block creation. Difficulty is set permanently to 1 for regtest.
Makes use of FAKECHAIN network type, but takes hard fork heights from mainchain
Default reserve_size in generate_blocks RPC call is now 1. If it is 0, the following error occurs 'Failed to calculate offset for'.
Queries hard fork heights info of other network types
rpc: add blockchain disk size to getinfo2018-06-20T22:48:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-06-17T21:07:15Zurn:sha1:e5592c4bab058e154f68858dcb41eed6c2f0f18a
This should help new nodes predict how much disk space will be
needed for a full sync
unit_tests/hardfork: add tests for get_voting_info()2018-05-30T00:49:58Zstoffustoffu@protonmail.ch2018-03-20T03:01:09Zurn:sha1:0321d1ac794b52233225a6a03001528ce6eea21c