monzero-core.git/tests/unit_tests/hardfork.cpp, branch v0.10.0

core: faster find_blockchain_supplement

2016-08-31T09:03:32Z

Since this queries block heights for blocks that may or may not exist, queries for non existing blocks would throw an exception, and that would slow down the loop a lot. 7 seconds to go through a 30 hash list. Fix this by adding an optional return block height to block_exists and using this instead. Actual errors will still throw an exception. This also cuts down on log exception spam.

move the rct commitments to the output_amounts database

2016-08-28T20:29:02Z

Since these are needed at the same time as the output pubkeys, this is a whole lot faster, and takes less space. Only outputs of 0 amount store the commitment. When reading other outputs, a fake commitment is regenerated on the fly. This avoids having to rewrite the database to add space for fake commitments for existing outputs. This code relies on two things: - LMDB must support fixed size records per key, rather than per database (ie, all records on key 0 are the same size, all records for non 0 keys are same size, but records from key 0 and non 0 keys do have different sizes). - the commitment must be directly after the rest of the data in outkey and output_data_t.

blockchain_db: add functions for adding/removing/getting rct commitments

2016-08-28T20:28:11Z

Fake outs set is now decided by the wallet

2016-08-11T13:35:27Z

This plugs a privacy leak from the wallet to the daemon, as the daemon could previously see what input is included as a transaction input, which the daemon hadn't previously supplied. Now, the wallet requests a particular set of outputs, including the real one. This can result in transactions that can't be accepted if the wallet happens to select too many outputs with non standard unlock times. The daemon could know this and select another output, but the wallet is blind to it. It's currently very unlikely since I don't think anything uses non default unlock times. The wallet requests more outputs than necessary so it can use spares if any of the returns outputs are still locked. If there are not enough spares to reach the desired mixin, the transaction will fail.

remove hf_starting_height db

2016-07-13T20:38:34Z

It's not really needed, it used to be an optimization for when that code was not using the db and needed to recalculate things fast on startup.

fix: error: -Werror=misleading-indentation

2016-05-18T14:54:41Z

Compilation of bitmonero on Arch with gcc 6.1 results in the following error: /home/mwo/bitmonero/tests/unit_tests/hardfork.cpp: In member function ‘virtual void TestDB::set_hard_fork_version(uint64_t, uint8_t)’: /home/mwo/bitmonero/tests/unit_tests/hardfork.cpp:132:5: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation] if (versions.size() <= height) versions.resize(height+1); versions[height] = version; This can be fixed by simply unfolding this line into three lines.

Merge branch 'performance' into master

2016-04-05T20:13:16Z

Cleanup

2016-04-05T20:05:24Z

drop obsolete remove_output() fix get_output_key(global), fix crash in blockchain_dump

tests: obligatory hardfork unit build fix after interface change

2016-03-26T23:44:04Z

New RPC and daemon command to get output histogram

2016-03-26T21:10:43Z

This is a list of existing output amounts along with the number of outputs of that amount in the blockchain. The daemon command takes: - no parameters: all outputs with at least 3 instances - one parameter: all outputs with at least that many instances - two parameters: all outputs within that many instances The default starts at 3 to avoid massive spamming of all dust outputs in the blockchain, and is the current minimum mixin requirement. An optional vector of amounts may be passed, to request histogram only for those outputs.