Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.2 2019-04-05T09:35:19Z 2019-04-05T09:35:19Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-04-04T00:15:57Z urn:sha1:089c7637a64652c8bcf6c437065237c23266d4a9 Use the actual block weight limit, assuming that weight is always greater or equal to size 2019-03-19T08:58:38Z Riccardo Spagni ric@spagni.net 2019-03-19T08:58:38Z urn:sha1:acc7211b5b2e1da17b5d83ae98bfc461365f6601 eef164f7 cryptonote_protocol_handler: search for syncing peers in "cruise mode" (moneromooo-monero) 2019-03-05T21:05:34Z binaryFate binaryfate@users.noreply.github.com 2019-03-05T21:05:34Z urn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6 2019-03-04T19:20:34Z Riccardo Spagni ric@spagni.net 2019-03-04T19:20:33Z urn:sha1:4466f4504e8bc41d353a6becce0526df8272bc1d 123fc2a2 i2p: initial support (Jethro Grassie) 2019-03-04T09:33:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-01-21T17:18:50Z urn: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. 2019-02-26T12:45:28Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-26T12:40:40Z urn:sha1:eef164f7cc805ecf1881812cebb972ad0ce58edb When all our outgoing peer slots are filled, we cycle one peer at a time looking for syncing peers until we have at least two such peers. This brings two advantages: - Peers without incoming connections will find more syncing peers that before, thereby strengthening network decentralization - Peers will have more resistance to isolation attacks, as they are more likely to find a "good" peer than they were before 2019-01-30T18:37:45Z Jethro Grassie jtg@xtrabass.com 2019-01-21T16:50:03Z urn:sha1:123fc2a25afaebe89b94c9806eb05033e021d807 2019-01-28T23:56:33Z Lee Clagett code@leeclagett.com 2018-12-16T17:57:44Z urn:sha1:973403bc9f54ab0722b67a3c76ab6e7bafbfeedc - Support for ".onion" in --add-exclusive-node and --add-peer - Add --anonymizing-proxy for outbound Tor connections - Add --anonymous-inbounds for inbound Tor connections - Support for sharing ".onion" addresses over Tor connections - Support for broadcasting transactions received over RPC exclusively over Tor (else broadcast over public IP when Tor not enabled). 2019-01-28T19:24:55Z Riccardo Spagni ric@spagni.net 2019-01-28T19:24:54Z urn:sha1:0daa00e0358b5c65be6266b5d9a1b70c8594c794 b6534c40 ringct: remove unused senderPk from ecdhTuple (moneromooo-monero) 7d375981 ringct: the commitment mask is now deterministic (moneromooo-monero) 99d946e6 ringct: encode 8 byte amount, saving 24 bytes per output (moneromooo-monero) cdc3ccec ringct: save 3 bytes on bulletproof size (moneromooo-monero) f931e16c add a bulletproof version, new bulletproof type, and rct config (moneromooo-monero) 2019-01-22T23:17:24Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-01-06T13:47:16Z urn:sha1:f931e16c6e45da6880c333cf1f355d7228c143d9 This makes it easier to modify the bulletproof format