monzero-core.git/src/cryptonote_config.h, branch v0.14.0.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.14.0.22019-02-12T12:16:40Zadd a bulletproof version, new bulletproof type, and rct config2019-02-12T12:16:40Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-01-06T13:47:16Zurn:sha1:f7f6760052db7194b8a0f01189d89246caf4882e
This makes it easier to modify the bulletproof format
ArticMine's new block weight algorithm2019-02-12T12:15:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-01-21T17:18:50Zurn: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.
Revert "Merge pull request #4472"2018-10-08T19:42:38ZRiccardo Spagniric@spagni.net2018-10-08T19:42:38Zurn:sha1:f5df0e272e0c0b513c6e24425e169683ad00d55c
This reverts commit b26ab0b5803af4ffe23de11a45e43877301a4902.
Merge pull request #44722018-10-06T09:15:43ZRiccardo Spagniric@spagni.net2018-10-05T21:13:31Zurn:sha1:b26ab0b5803af4ffe23de11a45e43877301a4902
02d3ef7b blocks: use auto-generated .c files instead of 'LD -r -b binary' (xiphon)
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:5ffb2ff9b7c301eda5811a939c705f26627c4735Add a define for the max number of bulletproof multi-outputs2018-09-11T13:37:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-30T19:44:51Zurn:sha1:7e67c52fa2a4ee68437a5fd906d9848a2f0a7150cryptonote_config: add get_config to refactor x = testnet ? config::testnet::X : stagenet ? config::stagenet::X : config::X2018-06-11T11:17:02Zstoffustoffu@protonmail.ch2018-06-11T03:16:29Zurn:sha1:08b85a8e00c0b3e5bb7c4d05861f8a42593cecf1core: fix use of uninitialised data2018-03-18T23:37:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-18T23:36:20Zurn:sha1:b1398fff4086762a15679a88badd2e324f37914eBump min ring size from 5 to 7 from v72018-03-07T13:19:04Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-07T10:37:31Zurn:sha1:38657fd0e9bfe67e30aa011d8ec0585e27a3af2dStagenet2018-03-05T02:55:05Zstoffustoffu@protonmail.ch2018-02-16T11:04:04Zurn:sha1:af773211cbc620a1be54f517bd60e587d58a7e93