monzero-core.git/tests/unit_tests/output_distribution.cpp, branch v0.18.4.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.22022-03-04T05:59:20ZCopyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009unit_tests: Fix uninitialized values2019-08-27T07:17:34ZMatyas Liptakmatyas@summitto.com2019-08-26T13:25:41Zurn:sha1:f56e16021729b6b4e92051051d5cd3cb3ba57660
- Initialize the `hash` in the `get_block_hash()` function of the
`output_distribution` unit test explicitly, to silence `valgrind`
warnings.
Merge pull request #54962019-05-07T15:30:27ZRiccardo Spagniric@spagni.net2019-05-07T15:30:27Zurn:sha1:9d91301faa27e5ed94dab99c5a157baa4ffb47da
0eb0d6b8 rpc: improve get_output_distribution (moneromooo-monero)
unit_tests: fix crash in debug in output_distribution test2019-04-25T22:49:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-25T21:25:23Zurn:sha1:a59c27465b12581702d9489e574f92f9141f158a
updating the block size limit needs recent block sizes,
so we feed it dummy ones
rpc: improve get_output_distribution2019-04-25T16:49:29Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-25T16:41:33Zurn:sha1:0eb0d6b8022b73cbb76e86a7022705f1e9173837
It can now handle small reorgs without having to rescan the
whole blockchain.
Also add a test for it.
ArticMine's new block weight algorithm2019-03-04T09:33:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-01-21T17:18:50Zurn:sha1:b8787f430262520a9e81267802b869b1a7cde245
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.
Note: the long term block weight is stored in the database, but not in the actual block itself,
since it requires recalculating anyway for verification.
tests: add unit tests for get_output_distribution2018-11-16T19:21:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-06T14:23:26Zurn:sha1:31d80027b5cc59b48205334a9e361c6a75099592