monzero-core.git/src/blockchain_db, branch v0.10.2.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.2.12017-02-21T17:38:18Zupdate copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359Merge pull request #17272017-02-21T09:27:15ZRiccardo Spagniric@spagni.net2017-02-21T09:27:15Zurn:sha1:49efd3add9f7b9bbcbd2526538846f6d8e58ac86
0288310e blockchain_db: add "raw" blobdata getters for block and transaction (moneromooo-monero)
Merge pull request #17242017-02-21T09:23:03ZRiccardo Spagniric@spagni.net2017-02-21T09:23:03Zurn:sha1:59d96eedd86c4e35879592f44af80ae32a35d447
cca95c1c blockchain_db: do not throw on expected partial results getting keys (moneromooo-monero)
Handle map resizes from other processes2017-02-18T22:22:24ZHoward Chuhyc@symas.com2017-02-18T21:00:55Zurn:sha1:2e9136767ee0a27b802c1cdc1e81d177a25be8fcCan't cache num_txs or num_outputs either2017-02-18T21:01:24ZHoward Chuhyc@symas.com2017-02-18T18:46:26Zurn:sha1:bf1348b7e2b2c72a6d40b23567afaa46b53e6cb7
Same reason as 3ff54bdd7a8b5e08e4e8ac17b7fff23ad3a82312
Add a few read txns to streamline2017-02-18T21:01:24ZHoward Chuhyc@symas.com2017-02-18T17:27:33Zurn:sha1:dc53e9eef22531902b8bbad7d9ec33cefc211e84
Slight perf gain, but mainly to reduce spam at loglevel 3
blockchain_db: add "raw" blobdata getters for block and transaction2017-02-13T21:11:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-01-15T16:05:55Zurn:sha1:0288310e3b4e777dd4d120898319192f957996a2
This speeds up operations such as serving blocks to syncing peers
blockchain_db: do not throw on expected partial results getting keys2017-02-13T19:05:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-02-13T19:05:30Zurn:sha1:cca95c1c7aa7506c7ec0df9846807050911152eb
When scanning for outputs used in a set of incoming blocks,
we expect that some of the inputs in their transactions will
not be found in the blockchain, as they could be in previous
blocks in that set. Those outputs will be scanned there at
a later point. In this case, we add a flag to control wehther
an output not being found is expected or not.
db_lmdb: fix bad height saved in tx data2017-02-11T10:16:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-02-11T10:16:18Zurn:sha1:f2986ccfc1f41023cd667dbb488a10df492eb8e7
The recent change to not keep separate track of the blockchain
height caused the reported height to jump early in the lmdb
transaction (when the block data is added to the blocks table),
rather than at the end, after everything succeeded. Since the
block data is added before the transaction data, this caused
the transaction data to be saved with a height one more than
its expected value.
Fix this by saving the block data last. This should have no
side effects.
extract some basic code from libcryptonote_core into libcryptonote_basic2017-02-08T13:45:15Zkenshi84kenshi84@protonmail.ch2017-01-26T15:07:23Zurn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96