monzero-core.git/src/blockchain_db/testdb.h, branch v0.14.1.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.02019-05-25T16:25:10Zcore: do not commit half constructed batch db txn2019-05-25T16:25:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-05-24T08:33:19Zurn:sha1:8f2a99d8ab1d3ea23c1968d6b3f1b43fd7faff89testdb: 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
blockchain_db: fix db txn ending too early2019-04-14T08:35:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-05T09:28:30Zurn:sha1:5e673c03fec66024027b94229fa2e317d7767a20
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.
cryptonote: rework block blob size sanity check2019-04-05T09:35:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-04T00:15:57Zurn:sha1:089c7637a64652c8bcf6c437065237c23266d4a9
Use the actual block weight limit, assuming that weight is always
greater or equal to size
Merge pull request #52562019-03-21T12:48:40ZRiccardo Spagniric@spagni.net2019-03-21T12:48:40Zurn:sha1:5ac46c5310d68faf05e2f525a9a0c9e834f4f404
4b21d38d blockchain: speed up getting N blocks weights/long term weights (moneromooo-monero)
blockchain: speed up getting N blocks weights/long term weights2019-03-08T12:04:14Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-02-21T00:13:21Zurn:sha1:4b21d38dfda29fe916700887c99d44edeb8fe06fUpdate 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6save some database calls when getting top block hash and height2019-03-05T11:58:05Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-20T20:19:39Zurn:sha1:79b4e9f3779796d9233e3e169f5c1086a49717ddAvoid repeated (de)serialization when syncing2019-03-05T11:57:55Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-11T14:51:03Zurn:sha1:b044d03a51e1dc64bebe2461813e0cfc50f71b0dArticMine'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.