monzero-core.git/src/cryptonote_protocol/block_queue.h, branch v0.13.0.0-RC1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.13.0.0-RC12018-07-20T15:05:56Zblock_queue: faster check whether a block was requested2018-07-20T15:05:56Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-19T14:36:07Zurn:sha1:704b60caf046e98ad6289043ab5f713d2ec3d5a1replace 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
Readd copyright starting date2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T23:55:52Zurn:sha1:84a7f6a4827f5baec6bb5cecbe11d4f61708b520Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880cryptonote_protocol: misc fixes to the new sync algorithm2017-08-21T20:57:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-18T19:14:23Zurn:sha1:70b8c6d77a6aaf90a6e84f3ec6f25bea3b163c40
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
cryptonote_protocol: kick idle synchronizing peers2017-08-16T21:24:50Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-16T18:27:16Zurn:sha1:7b747607566aa62460a4b4a278f2f8eb86f18bc2
In case they dropped off downloading for any reason, they'll get
sent to download again.
protocol: fix reorgs while syncing2017-08-12T10:22:42Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-12T09:59:27Zurn:sha1:08abb670e1d8c2d459dcd49ca02785a8cebc7b8bcryptonote_protocol: retry stale spans early2017-08-07T08:33:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-07-11T20:48:54Zurn:sha1:f57ee382b812e0dcd103023135934e601f9582aa
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).
cryptonote_protocol_handler: sync speedup2017-08-07T08:33:04Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-07-02T21:41:15Zurn:sha1:5be43fcdbad5ed034b07831473e07f47b7b10947
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.