monero.git - Monero: the secure, private, untraceable cryptocurrency

Age	Commit message (Collapse)	Author	Files	Lines
2020-05-06	Update copyright year to 2020	SomaticFanatic	1	-1/+1
	Update copyright year to 2020
2020-02-27	blockchain_db: faster fetching of consecutive txes	moneromooo-monero	1	-0/+1
	Useful for wallet refresh or node sync
2020-01-25	Merge pull request #6140	Alexander Blair	1	-0/+1
	08635a08 blockchain: speedup fetching pruned contiguous tx blobs (moneromooo-monero)
2019-11-15	blockchain: speedup fetching pruned contiguous tx blobs	moneromooo-monero	1	-0/+1
	About twice as fast, very roughly
2019-11-02	Adding support for hidden (anonymity) txpool	Lee Clagett	1	-5/+5

2019-07-24	Merge pull request #5524	luigi1111	1	-0/+7
	06b8f29 blockchain: keep alternative blocks in LMDB (moneromooo-monero)
2019-05-25	core: do not commit half constructed batch db txn	moneromooo-monero	1	-0/+1

2019-05-08	blockchain: keep alternative blocks in LMDB	moneromooo-monero	1	-0/+7
	Alternative blocks are cleared on startup unless --keep-alt-blocks is passed on the command line
2019-04-17	testdb: add override keyword where missing	stoffu	1	-101/+100
	and delete obsolete BlockchainBDB::get_tx_output_indices along the way
2019-04-14	blockchain_db: fix db txn ending too early	moneromooo-monero	1	-3/+7
	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.
2019-04-05	cryptonote: rework block blob size sanity check	moneromooo-monero	1	-0/+3
	Use the actual block weight limit, assuming that weight is always greater or equal to size
2019-03-21	Merge pull request #5256	Riccardo Spagni	1	-0/+2
	4b21d38d blockchain: speed up getting N blocks weights/long term weights (moneromooo-monero)
2019-03-08	blockchain: speed up getting N blocks weights/long term weights	moneromooo-monero	1	-0/+2

2019-03-05	Update 2019 copyright	binaryFate	1	-1/+1

2019-03-05	save some database calls when getting top block hash and height	moneromooo-monero	1	-1/+1

2019-03-05	Avoid repeated (de)serialization when syncing	moneromooo-monero	1	-1/+1

2019-03-04	ArticMine's new block weight algorithm	moneromooo-monero	1	-0/+152
	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.4LongTermEffectiveMedianBlockWeight) 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)), 50LongTermEffectiveMedianBlockWeight) 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.