monzero-core.git/src/cryptonote_core/blockchain.cpp, branch v0.9.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.02015-12-31T06:39:56Zupdated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51ablockchain: kill ioservice on scope end, rather than manually2015-12-30T16:08:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T16:08:30Zurn:sha1:576effe11a513507b14275c7a2e6fc3b18de5e17
This ensures this will be done without fail, as the error prone
matching of every return with a call to KILL_IOSERVICE leads to
hard to debug corruption when one is missing.
Merge pull request #5722015-12-30T07:38:41ZRiccardo Spagniric@spagni.net2015-12-30T07:38:41Zurn:sha1:fd36eea6ddc23d223593adb235b8e13a58ac11ef
b39aae7 Tweak 45800a25e9374e63caaabba05c89585c86acd668 (hyc)
4a5a5ff blockchain: always stop the ioservice before returning (moneromooo-monero)
78b65cf db_lmdb: safety close db at exit (moneromooo-monero)
45800a2 db_lmdb: fix a strdup/delete[] mistmatch (moneromooo-monero)
blockchain: always stop the ioservice before returning2015-12-28T22:47:46Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-28T19:53:07Zurn:sha1:4a5a5ff1573cc6a1081b28ef8611ca8bf8417800
Fixes a use after free
blockchain: remove obsolete containers2015-12-26T18:01:24Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-26T18:01:24Zurn:sha1:b0541a56eb0f3b07eb482726c3d99310e476a9fablockchain: Fix height in call to on_blockchain_dec2015-12-26T18:00:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-26T18:00:45Zurn:sha1:18a5211173346f418efbd8f8917da0b6acd47017
It was a noop anyway
blockchain: fix a few block addition bugs2015-12-25T22:13:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:13:38Zurn:sha1:f33a88cfc17177e3a079ee2226df9674dfa2d138
If the block reward was too high, the verification failed flag
was set, but the function continued. The code which was supposed
to trap this flag and return failure failed to trap it, and,
while the block was not added to the chain, the function would
return success.
The reason for avoiding returning when the block reward problem
was detected was to be able to return any transactions to the
pool if needed. This is now mooted by moving the transaction
return code to a separate function, which is now called at all
appropriate points, making the logic much simpler, and hopefully
correct now.
We also move the hard fork version check after the prev_id check,
as block which does not go on the top of the chain might not
have the expected version there, without being invalid just for
this reason.
Last, we trap the case where a block fails to be added due to
using already spent key images, to set the verification failed
flag.
blockchain: fix an off by one error in unlocked time check2015-12-25T22:12:52Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:12:52Zurn:sha1:a9ff11c8167ac52a4f120d02edf45ea0feac411cblockchain: reinstate double spending checks in check_tx_inputs2015-12-25T22:11:21Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:11:21Zurn:sha1:f294be35bce2fff97d85a657347871685990f792
This fixes some double spending tests.
This may or may not be unneeded in normal (non test) circumstances,
to be determined later. Keeping these for now may be slower, but safer.
blockchain: make some flag twiddling code closer to the original2015-12-25T22:10:27Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:10:27Zurn:sha1:737b6d6cf5b46a68304a8f9f83e262e560c33c0a
Probably paranoid and unnecessary