monzero-core.git/src/cryptonote_basic/connection_context.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-03-17T15:56:04ZMerge pull request #51902019-03-17T15:56:04ZRiccardo Spagniric@spagni.net2019-03-17T15:56:04Zurn:sha1:848591c4d85ae73c42b3317d9dab192267bc2737
551104fb daemon: add --public-node mode, RPC port propagation over P2P (xiphon)
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6daemon: add --public-node mode, RPC port propagation over P2P2019-02-24T23:40:23Zxiphonxiphon@protonmail.com2019-02-24T08:47:49Zurn:sha1:551104fbf1d2d82cad57d5ea240d1b7be2810ea1Pruning2019-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.
replace std::list with std::vector on some hot paths2018-06-26T21:14:21Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-15T23:16:02Zurn:sha1:ed2c81ed95be71bace897e62a0c241068cfde7be
also use reserve where appropriate
connection_context: remove "state_" prefix from state names2018-04-28T18:56:28Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-28T18:55:23Zurn:sha1:9cc0d4220fd7b13c3b2f15e7cb8b06f6f1b0e2fb
It's redundant and makes it easier to print them in columns
connection_context: initialize m_last_request_time to current time2018-02-04T13:13:08Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-04T13:11:34Zurn:sha1:b81e276cab0e41b42b9272e9fed47e1534480b5c
This prevents spurious early peer drops
Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880connection_context: initialize m_callback_request_count to 02017-09-27T10:43:12Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-19T14:58:37Zurn:sha1:15e62581366af2bd3656654038896d6bbb94d450move checkpoints in a separate library2017-09-25T20:16:26Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-10T16:35:59Zurn:sha1:5d65a75b69e0e83e69384461f26111666d6bf9ae