Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.1 2017-08-21T20:57:19Z 2017-08-21T20:57:19Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-18T19:14:23Z urn:sha1:70b8c6d77a6aaf90a6e84f3ec6f25bea3b163c40 Fix sync wedge corner case: It could happen if a connection went into standby mode, while it was the one which had requested the next span, and that span was still waiting for the data, and that peer is not on the main chain. Other peers can then start asking for that data again and again, but never get it as only that forked peer does. And various other fixes 2017-08-16T21:24:50Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-16T18:27:16Z urn:sha1:7b747607566aa62460a4b4a278f2f8eb86f18bc2 In case they dropped off downloading for any reason, they'll get sent to download again. 2017-08-09T19:49:24Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-09T19:49:24Z urn:sha1:f90bbe2a5cdbd438a4b2c5e4bbfda29e2b752a1b When a node is dropped, we stop considering its claimed blockchain height as a factor in the target height calculation. This prevents a runaway chain from being still thought to be the target even if the nodes carrying it are dropped. 2017-08-07T08:33:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-07-02T21:41:15Z urn:sha1:5be43fcdbad5ed034b07831473e07f47b7b10947 A block queue is now placed between block download and block processing. Blocks are now requested only from one peer (unless starved). Includes a new sync_info coommand. 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-12T17:17:30Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-12T17:17:30Z urn:sha1:8bdc86beb4c17b6970f25f00d35fe45977681956 In particular, the prepare_handle_incoming_blocks call is pretty lengthy, and entirely pointless in the common case where several different connections will prepare the exact same blocks. 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2017-01-16T00:25:46Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-01T16:34:23Z urn:sha1:5833d66f6540e7b34e10ddef37c2b67bd501994b This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. 2016-12-04T20:28:22Z Riccardo Spagni ric@spagni.net 2016-12-04T20:28:22Z urn:sha1:f2ea2afb772d4377450d2e79ebf44d1e1ffa3ec6 f4772bae Fix a few minor typos (Pierre Boyer) 2016-12-04T13:13:54Z Pierre Boyer pierre.s.boyer@gmail.com 2016-12-04T13:13:54Z urn:sha1:f4772bae812cdab9cca3864d79cdbec7abe5a114