9 Commits (3a4008f0fc56b921924f16cd70dbfa121b4ec46d)

Author	SHA1	Message	Date
Riccardo Spagni	4308a2e173	Merge pull request #5318 ... 1a91385e block_weight: fix python 2/3 compatibility (moneromooo-monero)	5 years ago
moneromooo-monero	1a91385eaf	block_weight: fix python 2/3 compatibility	5 years ago
moneromooo-monero	9b687c7873	blockchain: simple cache for the long term block weights	5 years ago
Riccardo Spagni	5ac46c5310	Merge pull request #5256 ... 4b21d38d blockchain: speed up getting N blocks weights/long term weights (moneromooo-monero)	5 years ago
moneromooo-monero	4b21d38dfd	blockchain: speed up getting N blocks weights/long term weights	5 years ago
moneromooo-monero	fa43b54780	tests: handle any cmake detected python interpreter	5 years ago
moneromooo-monero	79b4e9f377	save some database calls when getting top block hash and height	5 years ago
moneromooo-monero	b044d03a51	Avoid repeated (de)serialization when syncing	5 years ago
moneromooo-monero	b8787f4302	ArticMine's new block weight algorithm ... 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.	5 years ago