Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.0 2017-02-27T22:28:45Z 2017-02-27T22:28:45Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-27T22:03:31Z urn:sha1:da18898f0e64a9bec75e10230038759ccf95205e These fields aren't used, and they'll actually be pruned in some cases 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2017-01-21T20:29:22Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-21T20:29:22Z urn:sha1:6cc7d261406ad38071065a79f66c4366f65b65ba 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. 2017-01-14T21:17:32Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-14T13:29:08Z urn:sha1:ba3968f6ce0459f0c0a767e4f54e7cb2c48955d9 Semantics can be checked early 2016-12-19T19:47:26Z Lee Clagett code@leeclagett.com 2016-12-19T19:47:26Z urn:sha1:e3639f5cc3bad93d8c2556026209e4cac338ada5 2016-12-12T23:01:20Z luigi1111 luigi1111w@gmail.com 2016-12-12T23:01:20Z urn:sha1:9d906159c3ae377cd403831d51c7e400644c0a77 And rangeProofs are on outputs... 2016-12-08T21:44:09Z Riccardo Spagni ric@spagni.net 2016-12-08T21:44:09Z urn:sha1:e6b05ed95a588f37a0c06802d201b06e7b208773 3b005275 ringct: add sc_check calls in MLSAG_Ver for ss and cc (moneromooo-monero) 2f1732a7 ringct: guard against bad data exceptions in worker threads (moneromooo-monero) 2016-12-07T22:41:21Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-12-07T22:41:21Z urn:sha1:3b00527500b08859a75cf94a78c55656bcc2f99e luigi1111's recommendation 2016-12-07T22:09:43Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-12-07T22:09:43Z urn:sha1:2f1732a7e5baf6661ef8d9573754f0388ecba56f If purported pubkeys aren't actually valid pubkeys, exceptions will fly. These will terminate if thrown in a worker thread. Guard against this.