aboutsummaryrefslogtreecommitdiff
path: root/src/cryptonote_protocol/block_queue.h (follow)
AgeCommit message (Collapse)AuthorFilesLines
2019-03-05Update 2019 copyrightbinaryFate1-1/+1
2019-01-22Pruningmoneromooo-monero1-6/+11
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.
2018-07-20block_queue: faster check whether a block was requestedmoneromooo-monero1-0/+6
2018-06-26replace std::list with std::vector on some hot pathsmoneromooo-monero1-10/+10
also use reserve where appropriate
2018-01-26Readd copyright starting datexmr-eric1-1/+1
2018-01-26Update 2018 copyrightxmr-eric1-1/+1
2017-08-21cryptonote_protocol: misc fixes to the new sync algorithmmoneromooo-monero1-1/+2
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-16cryptonote_protocol: kick idle synchronizing peersmoneromooo-monero1-0/+1
In case they dropped off downloading for any reason, they'll get sent to download again.
2017-08-12protocol: fix reorgs while syncingmoneromooo-monero1-3/+3
2017-08-07cryptonote_protocol: retry stale spans earlymoneromooo-monero1-0/+1
Connections can be dropped by the net_node layer, unbeknownst to cryptonote_protocol, which would then not flush any spans scheduled to that connection, which would cause it to be only downloaded again once it becomes the next span (possibly after a small delay if it had been requested less than 5 seconds ago).
2017-08-07cryptonote_protocol_handler: sync speedupmoneromooo-monero1-0/+96
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.