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-19T15:21:57Z 2019-02-19T15:21:57Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-19T11:00:27Z urn:sha1:395eb9217a72b9b1579c8ba1c959f428b21d26b6 It seems to be buggy on reorgs, and prevents the use of a blockchain with two nodes. We'll speed this up again if/when the need arises. 2019-02-14T19:25:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-14T15:36:13Z urn:sha1:0b0fb709c3e2eca883236ffcccdc6cb08946d3e8 2019-02-12T12:16:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-01-09T14:29:28Z urn:sha1:7d2f817f5ea6091600d484b84799da0d27a8370c This will trigger if a reorg is seen. This may be used to do things like stop automated withdrawals on large reorgs. %s is replaced by the height at the split point %h is replaced by the height of the new chain %n is replaced by the number of new blocks after the reorg 2019-02-12T12:16:02Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-09-20T13:31:45Z urn:sha1:1168e8d5d529069093aee652472fd8ca9a8c533c The warning threshold is set to allow a false positive every ten days on average. 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-08T19:42:38Z Riccardo Spagni ric@spagni.net 2018-10-08T19:42:38Z urn:sha1:f5df0e272e0c0b513c6e24425e169683ad00d55c This reverts commit b26ab0b5803af4ffe23de11a45e43877301a4902. 2018-10-06T09:15:43Z Riccardo Spagni ric@spagni.net 2018-10-05T21:13:31Z urn:sha1:b26ab0b5803af4ffe23de11a45e43877301a4902 02d3ef7b blocks: use auto-generated .c files instead of 'LD -r -b binary' (xiphon) 2018-09-29T08:44:18Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-09-03T14:19:15Z urn:sha1:734030046055f521a73e59b50fa2a16f48e34c8d Those take a command line of the form "A [B]", with A being the name (and optional path, if not in the caller's CWD, but fully qualified path is recommended, avoids possible security issues) to a program, and optional arguments. Any occurence of the two character string "%s" will be replaced by the hash of the block or transaction which triggered the notification. Tokenization is barebones. If you want things like pipes, calls to paths with spaces, etc, then use a script (though exec time will suffer). block-notify is called when a new block is added onto the chain. tx-notify is called when a new transaction happens with the wallet as source and/or destination. It is the notification program's responsibility to determine what to do in those cases. Note that this is asynchronous, so it is very possible that: - the notification programs will be run out of order - several events happen before the notification for the first one A Windows port would be nice if someone wants to make one. 2018-09-14T10:51:45Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-08-13T16:18:32Z urn:sha1:be001326d1baac0b00d79d2d0a7f42662dc1be1f 2018-09-11T13:38:07Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-07-18T21:24:53Z urn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735