monzero-core.git/src/cryptonote_core/blockchain.cpp, branch v0.14.0.0 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.14.0.0 2019-02-20T16:17:07Z update quick sync checkpoints and hash 2019-02-20T16:17:07Z Riccardo Spagni ric@spagni.net 2019-02-20T16:17:07Z urn:sha1:392f0858c632f9088be603515d1031800796e10e blockchain: remove buggy long term block weight cache 2019-02-19T15:21:57Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-19T11:00:27Z urn:sha1:395eb9217a72b9b1579c8ba1c959f428b21d26b6 It seems to be buggy on reorgs, and prevents the use of a blockchain with two nodes. We'll speed this up again if/when the need arises. blockchain: fix block template creation race 2019-02-18T15:43:08Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-18T15:43:08Z urn:sha1:0c0f6034c099aadbb63c42c604beb8ba853a55e4 If two create_block_template are called at nearly the same time, and a block is added at nearly the same time, this could happen: - the blockchain top block is B0 - thread 1 enters create_block_template, takes blockchain lock - thread 1 creates a fresh block referencing prev block B0 - thread 1 releases blockchain lock - thread 0 adds a new block - thread 0 enters create_block_template - thread 0 updates block template - thread 1 takes txpool lock and continues creating block template - thread 1 overwrites block template with previous data blockchain: fix long term weight addition on pop/init 2019-02-18T12:46:32Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-18T12:44:52Z urn:sha1:1d62855044eed34f0184a468b90d63414c2a9ebc blockchain: fix m_long_term_block_weight_height initialization 2019-02-15T13:01:56Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-15T13:01:56Z urn:sha1:7aa0cc58e2a17fe0531c8ae192cb0e695e02d92a Also check return of that function, it can now return error blockchain: forbid older BP rct versions from v11 2019-02-15T10:20:23Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-15T10:20:23Z urn:sha1:bd7f82515b6e25818fc622e39e7a8fb948875f9f Fix v3/v4 db conversion 2019-02-15T01:21:37Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-14T22:56:51Z urn:sha1:f9d820ada1fecccf3b524660d25256cf77845014 Build fixes for some platforms 2019-02-14T19:25:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-14T15:36:13Z urn:sha1:0b0fb709c3e2eca883236ffcccdc6cb08946d3e8 blockchain: add v10 fork heights 2019-02-14T14:56:19Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-02-10T09:54:49Z urn:sha1:3ac3366a6e5d2d27345f9141d7dc19bc61f12027 cryptonote: Fix enum check in expand_transaction_2 2019-02-14T14:44:03Z Tom Smeding tom.smeding@gmail.com 2019-02-01T14:20:13Z urn:sha1:041af9545f9422b75a9015636d44665b129d7d22 This was noticed because GCC warned about using an enum value in a boolean context.