monzero-core.git/src/blockchain_db/lmdb/db_lmdb.cpp, branch v0.10.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.02016-08-31T09:03:32Zcore: faster find_blockchain_supplement2016-08-31T09:03:32Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-30T15:39:33Zurn:sha1:6cf8ca2a7f3e11ca5559018dfc9b20869c07cdce
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.
db_lmdb: fix reorg with "halfway rct" coinbase outputs2016-08-29T21:44:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-29T21:44:17Zurn:sha1:1cdba42a77f7dfae3028c4bf106e247ea7c033fdmove the rct commitments to the output_amounts database2016-08-28T20:29:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-29T18:55:49Zurn:sha1:59a66e209a844ac6d4221f7c04141b32fa2823c3
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.
add rct to the protocol2016-08-28T20:28:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-15T22:37:13Zurn:sha1:dc4aad7eb5fffa450d4c5eb094cf962e45b2f43a
It is not yet constrained to a fork, so don't use on the real network
or you'll be orphaned or rejected.
db_lmdb: update reset for recent db changes2016-08-28T20:28:35Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-25T08:59:21Zurn:sha1:211d1db7621ca1a7f98de31b584be3edd7aa95ca
- we need to drop the new m_tx_indices database
- we reset the version to current version
This fixes the core tests failing to initialize.
blockchain_db: add functions for adding/removing/getting rct commitments2016-08-28T20:28:11Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-04T13:18:37Zurn:sha1:eb56d0f9941d4aed9d89a20007221cecd1dc6cbcdb_lmdb: do not try to modify the database in read only mode2016-08-26T18:33:25Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-26T18:33:25Zurn:sha1:f88029e72afa2b53455568209be1001c1bf36769Merge pull request #9482016-08-11T20:43:14ZRiccardo Spagniric@spagni.net2016-08-11T20:43:14Zurn:sha1:0faf572db890c8bed9e5e4a7a21cd7d46d6f53d2
11dc091 Fake outs set is now decided by the wallet (moneromooo-monero)
1593553 new unlocked parameter to output_histogram (moneromooo-monero)
db_lmdb: errors dropping hf starting height db on reset are not fatal2016-08-10T09:50:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-10T09:50:17Zurn:sha1:240864f52945aed323c96377376155c879d7439e
This db is now dropped unconditionally, so may or may not be there
in the first place.
new unlocked parameter to output_histogram2016-08-01T21:16:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-01T21:16:00Zurn:sha1:1593553e03aef8d44621aaf79a33ba25f69a2bd7
This constrains the number of instances of any amount
to the unlocked ones (as defined by the default unlock time
setting: outputs with non default unlock time are not
considered, so may be counted as unlocked even if they are
not actually unlocked).