monzero-core.git/src/cryptonote_core/blockchain.h, 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: remove obsolete containers2015-12-26T18:01:24Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-26T18:01:24Zurn:sha1:b0541a56eb0f3b07eb482726c3d99310e476a9fablockchain: 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 bitflipping test with quantized block rewards2015-12-25T22:07:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:07:58Zurn:sha1:81cb0fcdccf08afd6f37d21ccfefb31131fd3950
Block reward may now be less than the full amount allowed.
This was breaking the bitflipping test.
We now keep track of whether a block which was accepted by the core
has a lower than allowed block reward, and allow this in the test.
Allow the wallet to access hard fork information2015-12-19T14:52:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-19T14:52:30Zurn:sha1:8ea7af1ba3ea74be52893a38ab9c7d5afdc90926
And make it change behavior slightly when close/after first hard fork
Replace tabs with two spaces for consistency with rest of codebase2015-12-15T14:22:06Zwarptangentwarptangent@tutanota.com2015-12-14T04:54:39Zurn:sha1:725acc7f17e47e0ea0e7e690f241ee8a286411ea
Remove trailing whitespace in same files.
add a --fakechain argument for tests2015-12-13T11:38:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-13T11:38:37Zurn:sha1:10da0a0b7cc70fad0ffde60bdd04926484fb043a
The core tests use the blockchain, and reset it to be able
to add test data to it. This does not play nice with the
databases, since those will save that data without an explicit
save call.
We add a fakechain flag that the tests will set, which tells
the core and blockchain code to use a separate database, as
well as skip a few things like checkpoints and fixup, which
only make sense for real data.
More changes for 2-min blocks2015-11-13T08:37:35ZJavier Smoothiamjaviersmooth@gmail.com2015-11-13T08:24:47Zurn:sha1:baf101ef4a05ae4d24ed717c16be929456775969
Use the correct block time for realtime fuzz on locktime
Use the correct block time to calculate next_difficulty on alt chains (will not work as-is with voting)
Lock unit tests to original block time for now
Remove some old/obsolete/unused code2015-10-27T10:01:20Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-10-27T10:01:20Zurn:sha1:4f873bcbaa7cbf8733ed9ffc4f136256cb90d447
git history's here if needed to get any of this back
Add functions to iterate through blocks, txes, outputs, key images2015-10-25T12:36:11Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-10-25T10:45:25Zurn:sha1:5f397e441275d0e282a371bcdeed963c9a9b69f1