| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
works.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
and all other associated IPC
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Could wrap more later.
|
| |
|
|
| |
It can now be set by some other code, and is thus tested
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Not doing so will prevent the new genesis block from being
reset if a switch past v1 had occured already.
|
| | |
|
| |
|
|
|
|
|
| |
Ensures the database is consistent.
Also simplifes blockchain_import in that verify mode off has less to
work around.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
This differs from the original CN code, and there seems to be
no reason to include the block itself, if it was found
|
| |
|
|
|
|
|
|
|
|
|
| |
- Blockchain should store if it's running on testnet or not
- moved loading compiled-in block hashes to its own function for clarity
- on handle_get_objects, should now correctly return false if a block's
transactions are missing
- replace instances of BOOST_FOREACH with C++11 for loops in Blockchain.
|
| |\
| |
| |
| |
| | |
7fc6fa3 wallet: forbid dust altogether in output selection where appropriate (moneromooo-monero)
5e1a739 blockchain: log number of outputs available for a new tx (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
bcac101 daemon: fix a few issues reported by valgrind (moneromooo-monero)
a7e8174 tx_pool: fix serialization of new relayed data (moneromooo-monero)
601ad76 hardfork: fix mixup in indexing variable in get_voting_info (moneromooo-monero)
444e22f blockchain: remove unused timer (moneromooo-monero)
7edfdd8 blockchain: fix m_sync_counter uninitialized variable use (moneromooo-monero)
d97582c epee: use generate_random_bytes for new random uuids (moneromooo-monero)
17c7c9c epee: remove dodgy random code that nobody uses (moneromooo-monero)
|
| | | | |
|
| | |/
| |
| |
| | |
It counts the number of blocks added since last zeroing
|
| |/
|
|
|
| |
It can flush a particular tx, or the whole pool (the RPC command
can flush a list of transactions too)
|
| |
|
|
|
| |
Some of it uses hardcoded height, which will need some thinking
for next (voted upon) fork.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| |
| |
| | |
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)
|
| | |
| |
| |
| | |
Fixes a use after free
|
| | | |
|
| |/
|
|
| |
It was a noop anyway
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
Probably paranoid and unnecessary
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
It was missing in the port to DB.
This is actually a noop, so should not have functional changes.
|
| |
|
|
|
| |
When rolling over more than one block, the db height will decrease,
but the split height should be constant, as per the original code.
|
| |
|
|
| |
It was present in the original code
|
| |
|
|
|
| |
This can happen when trying to find an amount that does not exist,
and fixes a core test.
|
| |
|
|
|
|
| |
The check was explicit in the original version, so it seems
safer to make it explicit here, especially as it is now done
implicitely in a different place, away from the original check.
|
| |
|
|
| |
And make it change behavior slightly when close/after first hard fork
|
| | |
|
| |
|
|
| |
The former is obsolete
|
| | |
|
| | |
|
| |
|
|
| |
Remove trailing whitespace in same files.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This makes it log the same height as the original code, which is
less confusing when comparing behaviors.
|
| | |
|