monzero-core.git/tests/unit_tests/blockchain_db.cpp, 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-04-14T08:35:38Zblockchain_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.
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6Avoid 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.
v8: per byte fee, pad bulletproofs, fixed 11 ring size2018-09-11T13:38:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-18T21:24:53Zurn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880move includes around to lessen overall load2017-12-16T22:46:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-11-25T22:25:05Zurn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341Replace deprecated tmpnam function.2017-03-30T02:32:00ZRandi Josephrandi@codehalo.com2017-03-29T18:07:49Zurn:sha1:933e08f2f3579ef29ff54f0e4d50163a2a8a19e4update copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359unit_tests: fix minor blockchain_db regression2017-02-14T18:56:42Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-02-14T18:55:01Zurn:sha1:b6a2230e6f6253426276cad577dc5dd8f192d139
Due to the change in ordering for adding block and tx data
to the database in f2986ccfc1f41023cd667dbb488a10df492eb8e7,
adding a block twice now throws TX_EXISTS, not BLOCK_EXISTS.