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-03-06T17:59:20Z 2019-03-06T17:59:20Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-03-06T17:58:34Z urn:sha1:3a23d2ae0de3f4a40c8954c9b2cf77b818276342 2019-03-06T00:06:30Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-03-01T16:14:51Z urn:sha1:20f732cd86f2c2198294bfba62e6e46ef382dec3 It's slow work, so let's not expose it 2019-02-18T06:24:00Z stoffu stoffu@protonmail.ch 2018-10-14T07:54:07Z urn:sha1:3b7967c660002c165470005d08e73f5f878e31f6 Fix for #4399. Also unifies code for serializing pruned tx to binary/json into one. (Cherry-picked from #4586) 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. 2018-10-20T18:44:04Z Riccardo Spagni ric@spagni.net 2018-10-20T18:44:04Z urn:sha1:3a44fa25828539c3efcf4e0285e394bbbcd392cf 742dec8d rpc: fix output distribution caching ignoring chain changes (moneromooo-monero) 2018-10-19T09:22:59Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-10-19T09:20:03Z urn:sha1:742dec8d6a8591961bfc35f4113fed7fceeaed78 0 is placeholder for whole chain, so we should compare chain height changes rather than chain-height-or-zero. Even this isn't totally foolproof if a blocks are popped and the same number added again, but it is much better as it prevents the data from slowly going out of sync. 2018-10-18T01:10:36Z stoffu stoffu@protonmail.ch 2018-10-17T23:01:56Z urn:sha1:d7ff707b528e8038ab3b63f11670fe443ec69f82 2018-09-21T18:46:00Z Riccardo Spagni ric@spagni.net 2018-09-21T18:46:00Z urn:sha1:fd74815f6562c3edb54fb9322ce77138992fa908 f77ce675 rpc: allow pruning of json encoded txs (cryptochangements34) 2018-09-21T18:41:53Z Riccardo Spagni ric@spagni.net 2018-09-21T18:41:53Z urn:sha1:0645dcdbdbdb7497445cae5e4772e5210fe5a1f4 ac934663 rpc: add a "is an update available" flag in get_info (moneromooo-monero) 2018-09-21T18:40:23Z Riccardo Spagni ric@spagni.net 2018-09-21T18:40:22Z urn:sha1:629db71593a5f84944dc5ccf63a943b099ee4b04 4f81cd3a rpc: add cumulative difficulty in block header data (moneromooo-monero)