monzero-core.git/src/blockchain_db/blockchain_db.cpp, branch v0.14.0.2 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.14.0.2 2019-02-12T12:15:54Z ArticMine's new block weight algorithm 2019-02-12T12:15:54Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-01-21T17:18:50Z urn:sha1:ebc60a098d40506fdd0c5974a8644728d502e024 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. v8: per byte fee, pad bulletproofs, fixed 11 ring size 2018-09-11T13:38:07Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-07-18T21:24:53Z urn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735 core: sync database based on bytes added, not blocks added 2018-08-12T16:13:46Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-08-01T10:09:35Z urn:sha1:b278b83860da5eaaa122c219ad8c63f641e41cd3 Blocks have a very wide range, whereas actual size is the relevant quantity to consider when syncing db: store cumulative rct output distribution in the db for speed 2018-07-13T10:37:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-05-22T13:46:30Z urn:sha1:45e419bd5c756337635feccec388efedf04f44ac This gets rid of the temporary precalc cache. Also make the RPC able to send data back in binary or JSON, since there can be a lot of data This bumps the LMDB database format to v3, with migration. db_lmdb: save pruned and prunable tx data separately 2018-05-23T21:48:12Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-10-01T10:24:33Z urn:sha1:b9389e582eb4e1806ce25a14fa492259c3d40dfc This bumps DB version to 2, migration code will run for v1 DBs Update 2018 copyright 2018-01-26T15:03:20Z xmr-eric eric@moneroeric.com 2018-01-07T05:05:16Z urn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880 fix a few leaks by throwing objects, not newed pointers to objects 2017-12-18T15:15:13Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-12-09T12:56:27Z urn:sha1:d753d716a6288ea9ecb4c9262b63ad804fa0a6e0 move includes around to lessen overall load 2017-12-16T22:46:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-11-25T22:25:05Z urn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341 blockchain_db: sanity check on tx/hash vector sizes 2017-11-15T10:02:23Z flozilla flozilla@users.noreply.github.com 2017-11-15T10:02:23Z urn:sha1:f9fad186080547a19fb3cc0f663763769b0830e5 It could trip on a corrupt/crafted file if the user has disabled input verification. remove "using namespace std" from headers 2017-11-14T16:56:10Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-10-10T14:47:08Z urn:sha1:383ff4f68943c5d998fba8caa20aee481583f214 It's nasty, and actually breaks on Solaris, where if.h fails to build due to: struct map *if_memmap;