blockchain_import: error out if preparing to handle blocks fails

2019-04-07T13:48:19Z

Coverity 197562

Make difficulty 128 bit instead of 64 bit

2019-03-24T21:03:19Z

Based on Boolberry work by: jahrsg cr.zoidberg

Update 2019 copyright

2019-03-05T21:05:34Z

core: avoid double parsing blocks after hoh

2019-03-05T11:58:13Z

Avoid repeated (de)serialization when syncing

2019-03-05T11:57:55Z

ArticMine's new block weight algorithm

2019-03-04T09:33:58Z

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.

remove some unused code

2018-11-23T15:37:36Z

Found by codacy.com

blockchain_utilities: fix logs and cout output colliding

2018-10-27T17:40:01Z

blocks: use auto-generated .c files instead of 'LD -r -b binary'

2018-10-21T22:12:00Z

Revert "Merge pull request #4472"

2018-10-08T19:39:54Z

This reverts commit 79d46c4d551a9b1261801960095bf4d24967211a, reversing changes made to c9fc61dbb56cca442c775faa2554a7460879b637.

monzero-core.git/src/blockchain_utilities/blockchain_import.cpp, branch v0.14.1.1