monzero-core.git/src/cryptonote_core/blockchain.cpp, branch v0.9.2 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.9.2 2016-03-11T15:09:50Z Use boost::thread instead of std::thread 2016-03-11T15:09:50Z Howard Chu hyc@symas.com 2016-03-11T12:25:28Z urn:sha1:b937a2c915861900d047d4d4a24af31c454e3540 and all other associated IPC Blockchain: Omit verbose time stats messages by default 2016-03-04T04:14:48Z warptangent warptangent@tutanota.com 2016-03-04T03:31:40Z urn:sha1:a49c355cae42fea4c8ee0c319969b47b0640713d This is already the default for the daemon, but by checking a command line argument and calling a Blockchain member function setter. Initialize the variable to false so it's not dependent on an external command-line argument check. This allows utilities like blockchain_import to have a reasonable default without code changes. Wrap some more actions in a larger read txn 2016-02-23T20:47:15Z Howard Chu highlandsun@gmail.com 2016-02-18T14:41:19Z urn:sha1:5a07cefe7bfb0000dcb078f8cfcb05d1709af8d2 read txn/cursor stuff 2016-02-23T20:47:15Z Howard Chu hyc@symas.com 2016-02-18T12:09:57Z urn:sha1:8cc7a36f0be2f90b62a6ffce840817e046e928a0 Could wrap more later. blockchain: initialize m_hardfork to NULL 2016-02-08T20:57:20Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-02-08T20:57:20Z urn:sha1:c7f82ec7694a48f8367b22393fabf677576b9cff It can now be set by some other code, and is thus tested core_tests: add tests for hard fork behaviors (MRL-0004) 2016-02-08T18:52:00Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-02-08T18:47:56Z urn:sha1:a333c42cdeab4675c22df25255313752d81a2d4e We also replace the --fakechain option with an optional structure containing details about configuration for the core/blockchain, for test purposes. This seems more future friendly. blockchain: reset hardfork object when resetting blockchain 2016-02-08T18:22:03Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-02-08T18:21:42Z urn:sha1:6c8e5c34598b4a9c7a80630fe2bb854ad5def016 Not doing so will prevent the new genesis block from being reset if a switch past v1 had occured already. Blockchain: Update comments on removing block 2016-02-08T17:28:25Z warptangent warptangent@tutanota.com 2016-02-08T16:19:24Z urn:sha1:e298b14a55c7f5792481a488104e6358127b6aa3 Move HardFork DB update to BlockchainDB::add_block() 2016-02-08T17:28:19Z warptangent warptangent@tutanota.com 2016-02-08T16:09:07Z urn:sha1:e02577f594ecd0a619ef3efaf65de90df9c20289 Ensures the database is consistent. Also simplifes blockchain_import in that verify mode off has less to work around. Make HardFork object available to BlockchainDB and derived DB implementations 2016-02-08T17:28:17Z warptangent warptangent@tutanota.com 2016-02-08T15:51:57Z urn:sha1:3800875406fecab5123564e58ddb698bce550441 This will later allow the HardFork object's DB update functions to be called when the DB transaction that persists across block add/remove is open.