12 Commits (aba46a7c5f0a892533abd3cc1a8b97cdf6b23fcc)

Author	SHA1	Message	Date
Hiroji Kiyotake	29e13fe96a	Merge branch 'dev-v0.6' into wow	5 years ago
moneromooo-monero	af1a741699	core: do not commit half constructed batch db txn	5 years ago
moneromooo-monero	4dcd3cd0b2	blockchain: keep alternative blocks in LMDB ... Alternative blocks are cleared on startup unless --keep-alt-blocks is passed on the command line	5 years ago
stoffu	5fafb90e91	testdb: add override keyword where missing ... and delete obsolete BlockchainBDB::get_tx_output_indices along the way	5 years ago
moneromooo-monero	5e673c03fe	blockchain_db: fix db txn ending too early ... The db txn in add_block ending caused the entire overarching batch txn to stop. Also add a new guard class so a db txn can be stopped in the face of exceptions. Also use a read only db txn in init when the db itself is read only, and do not save the max tx size in that case.	5 years ago
moneromooo-monero	089c7637a6	cryptonote: rework block blob size sanity check ... Use the actual block weight limit, assuming that weight is always greater or equal to size	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
binaryFate	1f2930ce0b	Update 2019 copyright	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