monzero-core.git/tests/unit_tests/hardfork.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:da9aa1f7f802552b9de459f331a2f39c84898009Remove unused variables in monero codebase2021-02-09T07:05:05ZKevin Barbourkevinbarbourd@gmail.com2021-01-23T09:38:50Zurn:sha1:85db1734e7dd456c1edb095a2c829527262b96c7
There are quite a few variables in the code that are no longer
(or perhaps never were) in use. These were discovered by enabling
compiler warnings for unused variables and cleaning them up.
In most cases where the unused variables were the result
of a function call the call was left but the variable
assignment removed, unless it was obvious that it was
a simple getter with no side effects.
Update copyright year to 20202020-05-07T02:36:54ZSomaticFanaticafdlkajdlfkj@aldkfjf.com2020-05-07T02:36:54Zurn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6
Update copyright year to 2020
testdb: add override keyword where missing2019-04-17T01:26:25Zstoffustoffu@protonmail.ch2019-04-09T09:38:53Zurn:sha1:5fafb90e91cf5288505e4b8a669bc8340eb906e7
and delete obsolete BlockchainBDB::get_tx_output_indices along the way
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6ArticMine'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:31d80027b5cc59b48205334a9e361c6a75099592core: avoid unnecessary tx/blob conversions2018-11-01T15:51:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-31T08:31:13Zurn:sha1:6ecc99ad1fd0f2b86641669077130394ab21e71cv8: 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