monzero-core.git/src/cryptonote_core/blockchain.h, branch v0.11.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.12017-10-22T10:19:53Zcore: fix failure to sync when a tx is already in the pool2017-10-22T10:19:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-29T20:34:10Zurn:sha1:bb11c9141238392ea4c2d54f850f656d027e8b8dToggle SAFE syncmode on and off automatically2017-08-20T15:30:28ZHoward Chuhyc@symas.com2017-08-19T18:36:51Zurn:sha1:9a859844f496158b8237bbd08ff0f608dc5a6385
If monerod is started with default sync mode, set it to SAFE after
synchronization completes. Set it back to FAST if synchronization
restarts (e.g. because another peer has a longer blockchain).
If monerod is started with an explicit sync mode, none of this
automation takes effect.
protocol: pass blockchain cumulative difficulty when syncing2017-08-15T20:03:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-12T14:24:39Zurn:sha1:827afcb7ea10eb2bf03ffb7ad2520f29cd53019f
Not used yet.
Merge pull request #22462017-08-15T18:47:32ZRiccardo Spagniric@spagni.net2017-08-15T18:47:32Zurn:sha1:12c70fedc0f35ee93236320614184000bc706931
d732c73e blockchain: remove a few unused variables (moneromooo-monero)
protocol: add checks for top block hard fork version2017-08-09T09:28:41Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-09T08:31:00Zurn:sha1:635929eaca6b376708d7c5fabf9b743b8a706981
We won't even talk to a peer which claims a wrong version
for its top block. This will avoid syncing to known bad
peers in the first place.
Also add IP fails when failing to verify a block.
Merge pull request #22252017-08-07T20:10:09ZRiccardo Spagniric@spagni.net2017-08-07T20:10:09Zurn:sha1:62610a3a53c8cab1f846aa37c5b4d7793541ae43
5d91b26c blockchain: skip checking tx semantics in embedded block hash range (moneromooo-monero)
blockchain: remove a few unused variables2017-08-03T10:26:55Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-03T10:26:55Zurn:sha1:d732c73e71232328f039311760359b85823116bcblockchain: skip checking tx semantics in embedded block hash range2017-07-30T08:48:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-07-30T08:45:55Zurn:sha1:5d91b26c0f8ab95aba984c97b8aed093601de8e7
If the txes are bad, this'll be picked up by the block hash mismatch
since the tx merkle root is part of the block hash.
blockchain: ensure all blocks get their longhash precalculated2017-07-27T17:18:49Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-07-27T17:18:49Zurn:sha1:91aa90fc7914d9ece44ff6179f126ae2e5ba848b
If the number of blocks to check was not a multiple of the
number of preparation threads, the last few blocks would
not be included in the threaded long hash calculation.
Those would still get calculated when the block gets added
to the chain, however, so this was only a tiny performance
hit, rather than a security bug.
Fix mismatch of parameter name between header file and implementation for set_user_options()2017-06-22T21:16:11ZJulien Klepatchjulien@julienklepatch.com2017-06-22T21:16:11Zurn:sha1:bdab3436d3cac28e0498b827fb28841b1638b343