monzero-core.git/src/cryptonote_core, 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-13T14:36:43ZMerge pull request #14372016-12-13T14:36:43ZRiccardo Spagniric@spagni.net2016-12-13T14:36:43Zurn:sha1:b1bdb4e5293d54da8625698e17fca934ee4dbdb9
655eafd1 bump version (Riccardo Spagni)
117194a3 update checkpoints (Riccardo Spagni)
39a9db9e update checkpoints (Riccardo Spagni)
blockchain: 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.
update checkpoints2016-12-12T22:24:48ZRiccardo Spagniric@spagni.net2016-12-12T22:24:48Zurn:sha1:39a9db9eb1494a774ab66fadfc0a14f157ab21deMerge pull request #14192016-12-10T12:48:56ZRiccardo Spagniric@spagni.net2016-12-10T12:48:56Zurn:sha1:930aceb24241d5f8f863fec585b7d338674bf0a0
f4a3ce15 Fix sending outputs from a tx with more than one pubkey (moneromooo-monero)
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)
Fix sending outputs from a tx with more than one pubkey2016-12-09T18:21:21Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-09T18:21:21Zurn:sha1:f4a3ce15c196c2e8c723ab459be69e60d7de6007
A bug in cold signing caused a spurious pubkey to be included
in transactions, so we need to ensure we use the correct one
when sending outputs from one of those.
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.
ringct: switch to Borromean signatures2016-12-04T21:54:11ZShen NoetherShen.Noether@gmx.com2016-11-17T23:17:21Zurn:sha1:76958fc75abc18c928474eea91ac05fd5e0fcb41Merge pull request #13982016-12-04T20:28:22ZRiccardo Spagniric@spagni.net2016-12-04T20:28:22Zurn:sha1:f2ea2afb772d4377450d2e79ebf44d1e1ffa3ec6
f4772bae Fix a few minor typos (Pierre Boyer)