monzero-core.git/src/blockchain_db/berkeleydb, branch crash-plMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=crash-pl2018-02-02T15:21:39Zblockchain_db: initialize m_open in base class ctor2018-02-02T15:21:39Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-02T15:21:39Zurn:sha1:ad11db9144f766d86d4aa4904eecd446fb670597
It's cleaner this way, since it's a base class field
Coverity 136568
Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880move includes around to lessen overall load2017-12-16T22:46:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-11-25T22:25:05Zurn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341update copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359extract some basic code from libcryptonote_core into libcryptonote_basic2017-02-08T13:45:15Zkenshi84kenshi84@protonmail.ch2017-01-26T15:07:23Zurn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96Use batch transactions when syncing2017-01-14T22:43:06ZHoward Chuhighlandsun@gmail.com2016-12-26T22:29:46Zurn:sha1:0693cff9251f91a05dd96b2f8910faea29cb29ce
Faster throughput while avoiding corruption. I.e., makes
running with --db-sync-mode safe more tolerable.
core: 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.
move 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.
remove hf_starting_height db2016-07-13T20:38:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-13T20:19:05Zurn:sha1:d7b681cd6518834ce9b76676980561cb8e235cff
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.
add a --max-concurrency flag2016-04-28T19:33:59Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-04-28T19:25:33Zurn:sha1:513a658c87b5fa23533a6b6db36e6d36af6a861d
It sets the max number of threads to use for a parallel job.
This is different that the number of total threads, since monero
binaries typically start a lot of them.