monzero-core.git/src/cryptonote_core/blockchain.cpp, branch v0.10.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.12016-12-13T02:13:23Zblockchain: fix reorganizations past a hard fork boundary2016-12-13T02:13:23Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-13T02:13:23Zurn:sha1:dd144b14bcdcd7679d201e762a1165dcdea13c29
After popping blocks from the old chain, the hard fork object's
notion of the current version was not in line with the new height,
causing the first blocks from the new chain to be rejected due
to a false expection of a newer version.
Merge pull request #14182016-12-10T12:48:39ZRiccardo Spagniric@spagni.net2016-12-10T12:48:39Zurn:sha1:0f99423080c22050c9198dc12a8cf908f8f5ecc0
dfbb85b6 blockchain: fix setting non trovial alternate chain as invalid (moneromooo-monero)
blockchain: fix setting non trovial alternate chain as invalid2016-12-08T22:26:27Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-08T22:26:27Zurn:sha1:dfbb85b6fef5daf26d5c1359245dec71606e6076
The wrong iterator was being used.
Also preincrement iterators to avoid possibly invalidating them,
I'm not sure this is necessary, but let's be safe.
blockchain: bring the v4 fork height one block forward2016-12-06T21:59:08Zluigi1111luigi1111w@gmail.com2016-12-06T21:46:54Zurn:sha1:648ea6bef1afb8e6eb6eb240987ce2e6f7ed3de6
This will ensure the early 0.10 daemons will barf at the fork
height, and not a bit later, which could be confusing.
Merge pull request #13982016-12-04T20:28:22ZRiccardo Spagniric@spagni.net2016-12-04T20:28:22Zurn:sha1:f2ea2afb772d4377450d2e79ebf44d1e1ffa3ec6
f4772bae Fix a few minor typos (Pierre Boyer)
Merge pull request #13972016-12-04T20:27:41ZRiccardo Spagniric@spagni.net2016-12-04T20:27:41Zurn:sha1:80863796807ecd524f4a76964b2d58167f819e26
3f7d6fb5 Fix delayed exit when syncing (moneromooo-monero)
Merge pull request #13922016-12-04T20:23:03ZRiccardo Spagniric@spagni.net2016-12-04T20:23:03Zurn:sha1:416f7fbd5f9f8218f72a73a090c4689163c3c2b6
204b1bff blockchain: use high bound block reward on error where appropriate (moneromooo-monero)
Fix a few minor typos2016-12-04T13:13:54ZPierre Boyerpierre.s.boyer@gmail.com2016-12-04T13:13:54Zurn:sha1:f4772bae812cdab9cca3864d79cdbec7abe5a114Fix delayed exit when syncing2016-12-04T12:27:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-04T12:27:45Zurn:sha1:3f7d6fb57d1bfb5ee806d3facc1261efe3ad14a0blockchain: use high bound block reward on error where appropriate2016-12-01T16:34:09Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-01T10:28:46Zurn:sha1:204b1bff626ea4be9c78136998c179ab18e63a4d
If the block reward to use for the fee calculation can't be
calculated (should not happen in practice), use a high bound,
so we use a fee overestimate that will be accepted by the network.