Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.1 2019-06-14T08:48:04Z 2019-06-14T08:48:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-03-08T19:17:20Z urn:sha1:fa4aa47ea06d935b41ef028eca9a246eb58bd162 Count transactions as well 2019-06-14T08:48:01Z anonimal anonimal@getmonero.org 2019-03-09T09:11:44Z urn:sha1:3c953d53696d9ccdd195e6a2f02578a154266882 Essentially, one can send such a large amount of IDs that core exhausts all free memory. This issue can theoretically be exploited using very large CN blockchains, such as Monero. This is a partial fix. Thanks and credit given to CryptoNote author 'cryptozoidberg' for collaboration and the fix. Also thanks to 'moneromooo'. Referencing HackerOne report #506595. 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-19T08:57:28Z Riccardo Spagni ric@spagni.net 2019-03-19T08:57:28Z urn:sha1:bf0f85221b748d2825fb6b169c8914ff17f40db7 a54e81e5 daemon: add '--no-sync' arg to optionally disable blockchain sync (xiphon) 2019-03-05T21:05:34Z binaryFate binaryfate@users.noreply.github.com 2019-03-05T21:05:34Z urn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6 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-02-25T03:22:14Z xiphon xiphon@protonmail.com 2019-02-25T01:31:45Z urn:sha1:a54e81e57213aa6a983401b20c3e150550a6e948 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-22T20:30:51Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-04-29T22:30:51Z urn:sha1:b750fb27b0f20e9443827732b69a504a76036430 The blockchain prunes seven eighths of prunable tx data. This saves about two thirds of the blockchain size, while keeping the node useful as a sync source for an eighth of the blockchain. No other data is currently pruned. There are three ways to prune a blockchain: - run monerod with --prune-blockchain - run "prune_blockchain" in the monerod console - run the monero-blockchain-prune utility The first two will prune in place. Due to how LMDB works, this will not reduce the blockchain size on disk. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. The third way will create a second database, a pruned copy of the original one. Since this is a new file, this one will be smaller than the original one. Once the database is pruned, it will stay pruned as it syncs. That is, there is no need to use --prune-blockchain again, etc. 2019-01-16T17:04:22Z Riccardo Spagni ric@spagni.net 2019-01-16T17:04:22Z urn:sha1:846362842c9893cdbbea1dd1f00931c50bb2df5e 85665003 epee: better network buffer data structure (moneromooo-monero)