Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=main 2026-06-21T20:27:37Z 2026-06-21T20:27:37Z selsta selsta@sent.at 2026-05-19T22:24:18Z urn:sha1:d2e4cbcda578152d9640a1aafa97a527f48a1380 2025-12-11T09:43:33Z tobtoht tob@featherwallet.org 2025-12-11T09:43:33Z urn:sha1:7baf2bde6ecad1e13848fdbd9d4db026ca0ff8fc 2021-04-16T18:54:20Z mj-xmr mjxmr@protonmail.com 2020-11-12T18:14:32Z urn:sha1:dc81e23e60f6539b5d273bd42024e765b6cdf2d5 2020-04-27T16:17:56Z Dusan Klinec dusan.klinec@gmail.com 2020-04-07T16:25:25Z urn:sha1:e509ede2aa7263cc49d3378bc8c833a62300211d - choice where to enter passphrase is now made on the host - use wipeable string in the comm stack - wipe passphrase memory - protocol optimizations, prepare for new firmware version - minor fixes and improvements - tests fixes, HF12 support 2017-11-03T15:27:50Z Tim L timo614@gmail.com 2017-11-03T15:24:28Z urn:sha1:0bf09154462a9030b4f288e0455198d775342a42 This branch fixes a file permission issue introduced by https://github.com/monero-project/monero/commit/69c37200aa87f100f731e755bdca7a0dc6ae820a 2017-10-30T17:55:56Z Tim L timo614@gmail.com 2017-10-24T13:26:05Z urn:sha1:69c37200aa87f100f731e755bdca7a0dc6ae820a 2017-09-25T14:47:59Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-09-09T09:59:44Z urn:sha1:11f71af56c11cf3b2ade879e633bf264ada07a7e CID 161879 2017-02-06T06:15:41Z Lee Clagett code@leeclagett.com 2017-02-05T22:48:03Z urn:sha1:ce7fcbb4aea884bb4bf433cf419ffa267f859c87 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-09-18T19:32:02Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-09-07T20:38:41Z urn:sha1:eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56 This is intended to catch traffic coming from a web browser, so we avoid issues with a web page sending a transfer RPC to the wallet. Requiring a particular user agent can act as a simple password scheme, while we wait for 0MQ and proper authentication to be merged.