monzero-core.git/src/daemon/command_parser_executor.h, branch v0.14.1.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.12019-05-21T16:17:34ZAdd ssl_options support to monerod's rpc mode.2019-05-21T16:17:34ZLee Clagettcode@leeclagett.com2019-05-22T04:09:11Zurn:sha1:fafc5c3692fb1579bf6b2cfa75dec70d3f51ae4cNew interactive daemon command 'print_net_stats': Global traffic stats2019-03-24T15:58:57Zrbrunner7rbrunner@dreamshare.ch2019-03-21T10:03:24Zurn:sha1:c23ea7962debe4e66fd3c0e7719117dcb7966d1fMerge pull request #51852019-03-17T15:55:32ZRiccardo Spagniric@spagni.net2019-03-17T15:55:32Zurn:sha1:429930534df43b8bef46a4a39dbfbc3d3b5939b0
59478c80 daemon: new mining_status command (moneromooo-monero)
daemon: new mining_status command2019-03-09T20:51:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-02-22T20:17:45Zurn:sha1:59478c80dd01d00e16994a77e36a94cdbe3c9412Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6Pruning2019-01-22T20:30:51Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-29T22:30:51Zurn: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.
add command pop_blocks2018-11-28T11:20:28ZJason Wongjason.hcwong@gmail.com2018-11-25T21:08:07Zurn:sha1:dc1c12528d5cf86759993614e1fdd7d7bf04ff15
add new public method to Blockchain and update according to code review
update after review: better lock/unlock, try catch and coding style
daemon: add a version command2018-04-13T17:47:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-13T17:12:17Zurn:sha1:35d1269faca070e1ec8906d0683896f937685b97Allow the number of incoming connections to be limited2018-01-29T00:14:02ZErik de Castro Lopoerikd@mega-nerd.com2018-01-20T21:44:23Zurn:sha1:32c0f908cd753f9319909e2f43d2b4657ebaf664
It was already possible to limit outgoing connections. One might want
to do this on home network connections with high bandwidth but low
usage caps.
Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880