monzero-core.git/src/blockchain_db/blockchain_db.cpp, branch v0.9.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.22016-02-23T20:47:15Zread txn/cursor stuff2016-02-23T20:47:15ZHoward Chuhyc@symas.com2016-02-18T12:09:57Zurn:sha1:8cc7a36f0be2f90b62a6ffce840817e046e928a0
Could wrap more later.
blockchain_db: pass hard fork object as a simple pointer2016-02-08T20:56:31Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-02-08T20:56:31Zurn:sha1:8649b9f1ef53375b40ac4a489bb8e56b82bb968cMove HardFork DB update to BlockchainDB::add_block()2016-02-08T17:28:19Zwarptangentwarptangent@tutanota.com2016-02-08T16:09:07Zurn:sha1:e02577f594ecd0a619ef3efaf65de90df9c20289
Ensures the database is consistent.
Also simplifes blockchain_import in that verify mode off has less to
work around.
Make HardFork object available to BlockchainDB and derived DB implementations2016-02-08T17:28:17Zwarptangentwarptangent@tutanota.com2016-02-08T15:51:57Zurn:sha1:3800875406fecab5123564e58ddb698bce550441
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.
BlockchainDB/LMDB: Refactor block-scope DB txn handling for add block2016-02-08T17:28:15Zwarptangentwarptangent@tutanota.com2016-02-08T16:32:36Zurn:sha1:fd46c96dce043cbf9f018f59ac9cedb12f6a4286
Move block-scope txn start and stop from BlockchainLMDB to BlockchainDB.
fixed copyrights with bad year references2015-12-31T06:37:27ZRiccardo Spagniric@spagni.net2015-12-31T06:37:27Zurn:sha1:810a11267c19512a49921c2e2884f6fd7dbf4206BlockchainDB: skip fixup check if read-only database2015-12-26T22:30:20Zwarptangentwarptangent@tutanota.com2015-12-26T22:27:35Zurn:sha1:ee9d71e9f94ba8571c44c889a70bda77c8961959BlockchainDB: Remove txs in reverse order2015-12-24T23:09:09Zwarptangentwarptangent@tutanota.com2015-12-24T23:01:00Zurn:sha1:d4c2fae2fb85e6064296a2467dc8ac28f431f3ee
Data should be removed in the reverse order it was added. Not doing so
breaks assumptions and can cause problems in other DB implementations.
This matches the order of tx removal in
blockchain_storage::purge_block_data_from_blockchain.
blockchain_db: fixup missing key images in early DB version2015-12-06T21:55:05Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-06T20:48:17Zurn:sha1:a98e976f9eabf2112a75347147becc1956ef8d66
Early DB versions did not store key images for inputs if the
transaction spending them had no outputs (ie, all fee). This
is not correct, as this would allow these outputs to be double
spent. This was fixed in 533acc30eda7792c802ea8b6417917fa99b8bc2b
a few months ago, but databases having synced blocks 2021612 and
685498 with a faulty version will be missing those key images
in the spent keys database. This code checks for this, and adds
those key images if they are missing.
blockchain_db: match tx addition semantics to original code2015-08-11T10:11:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-08-11T10:09:09Zurn:sha1:e63b85496790b458ac8b49d9d26c9de75b84859c
The original code removed key images from a tx from the blockchain
when an non to-key nor gen input was found in that tx. Additionally,
the remainder of the tx data was added to the blockchain only after
the double spend check passed.