aboutsummaryrefslogtreecommitdiff
path: root/src/blockchain_db/blockchain_db.h
Commit message (Collapse)AuthorAgeFilesLines
* persist asset outputs and spent key imagescenobite pinhead5 hours1-0/+14
|
* persist experimental asset registry in LMDBcenobite pinhead5 hours1-0/+8
|
* Fix use of rtxn without a mdb_txn_safe wrapperHoward Chu2022-07-221-7/+9
|
* Copyright: Update to 2022mj-xmr2022-03-041-1/+1
|
* rpc: limit the number of txes for get_blocks.binmoneromooo-monero2020-12-291-3/+6
|
* Avoid some temporary strings when reading off the databasemoneromooo-monero2020-08-171-6/+6
|
* Merge pull request #6354Alexander Blair2020-08-091-2/+3
|\ | | | | | | 67ade8005 Add randomized delay when forwarding txes from i2p/tor -> ipv4/6 (Lee Clagett)
| * Add randomized delay when forwarding txes from i2p/tor -> ipv4/6Lee Clagett2020-05-151-2/+3
| |
* | Merge pull request #6534Alexander Blair2020-07-191-0/+10
|\ \ | | | | | | | | | 7bd66b01b daemon: guard against rare 'difficulty drift' bug with checkpoints and recalculation (stoffu)
| * | daemon: guard against rare 'difficulty drift' bug with checkpoints and ↵stoffu2020-06-091-0/+10
| |/ | | | | | | | | | | recalculation On startup, it checks against the difficulty checkpoints, and if any mismatch is found, recalculates all the blocks with wrong difficulties. Additionally, once a week it recalculates difficulties of blocks after the last difficulty checkpoint.
* / Update copyright year to 2020SomaticFanatic2020-05-061-1/+1
|/ | | | Update copyright year to 2020
* Adding Dandelion++ support to public networks:Lee Clagett2020-03-261-2/+6
| | | | | | - New flag in NOTIFY_NEW_TRANSACTION to indicate stem mode - Stem loops detected in tx_pool.cpp - Embargo timeout for a blackhole attack during stem phase
* blockchain_db: faster fetching of consecutive txesmoneromooo-monero2020-02-271-0/+19
| | | | Useful for wallet refresh or node sync
* Merge pull request #6140Alexander Blair2020-01-251-0/+16
|\ | | | | | | 08635a08 blockchain: speedup fetching pruned contiguous tx blobs (moneromooo-monero)
| * blockchain: speedup fetching pruned contiguous tx blobsmoneromooo-monero2019-11-151-0/+16
| | | | | | | | About twice as fast, very roughly
* | Change to Tx diffusion (Dandelion++ fluff) instead of floodingLee Clagett2019-11-041-1/+1
| |
* | Adding support for hidden (anonymity) txpoolLee Clagett2019-11-021-8/+41
|/
* Merge pull request #5915luigi11112019-10-081-1/+2
|\ | | | | | | 8330e77 monerod can now sync from pruned blocks (moneromooo-monero)
| * monerod can now sync from pruned blocksmoneromooo-monero2019-09-271-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If the peer (whether pruned or not itself) supports sending pruned blocks to syncing nodes, the pruned version will be sent along with the hash of the pruned data and the block weight. The original tx hashes can be reconstructed from the pruned txes and theur prunable data hash. Those hashes and the block weights are hashes and checked against the set of precompiled hashes, ensuring the data we received is the original data. It is currently not possible to use this system when not using the set of precompiled hashes, since block weights can not otherwise be checked for validity. This is off by default for now, and is enabled by --sync-pruned-blocks
* | Removed Berkeley DB and db switching logicJesus Ramirez2019-09-161-2/+1
|/
* Merge pull request #5524luigi11112019-07-241-1/+64
|\ | | | | | | 06b8f29 blockchain: keep alternative blocks in LMDB (moneromooo-monero)
| * blockchain: keep alternative blocks in LMDBmoneromooo-monero2019-05-081-1/+64
| | | | | | | | | | Alternative blocks are cleared on startup unless --keep-alt-blocks is passed on the command line
* | core: do not commit half constructed batch db txnmoneromooo-monero2019-05-251-0/+15
|/
* blockchain_db: fix db txn ending too earlymoneromooo-monero2019-04-141-3/+52
| | | | | | | | | | The db txn in add_block ending caused the entire overarching batch txn to stop. Also add a new guard class so a db txn can be stopped in the face of exceptions. Also use a read only db txn in init when the db itself is read only, and do not save the max tx size in that case.
* cryptonote: rework block blob size sanity checkmoneromooo-monero2019-04-051-0/+14
| | | | | Use the actual block weight limit, assuming that weight is always greater or equal to size
* Merge pull request #5256Riccardo Spagni2019-03-211-0/+22
|\ | | | | | | 4b21d38d blockchain: speed up getting N blocks weights/long term weights (moneromooo-monero)
| * blockchain: speed up getting N blocks weights/long term weightsmoneromooo-monero2019-03-081-0/+22
| |
* | Update 2019 copyrightbinaryFate2019-03-051-1/+1
|/
* save some database calls when getting top block hash and heightmoneromooo-monero2019-03-051-1/+3
|
* Avoid repeated (de)serialization when syncingmoneromooo-monero2019-03-051-4/+4
|
* ArticMine's new block weight algorithmmoneromooo-monero2019-03-041-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This curbs runaway growth while still allowing substantial spikes in block weight Original specification from ArticMine: here is the scaling proposal Define: LongTermBlockWeight Before fork: LongTermBlockWeight = BlockWeight At or after fork: LongTermBlockWeight = min(BlockWeight, 1.4*LongTermEffectiveMedianBlockWeight) Note: To avoid possible consensus issues over rounding the LongTermBlockWeight for a given block should be calculated to the nearest byte, and stored as a integer in the block itself. The stored LongTermBlockWeight is then used for future calculations of the LongTermEffectiveMedianBlockWeight and not recalculated each time. Define: LongTermEffectiveMedianBlockWeight LongTermEffectiveMedianBlockWeight = max(300000, MedianOverPrevious100000Blocks(LongTermBlockWeight)) Change Definition of EffectiveMedianBlockWeight From (current definition) EffectiveMedianBlockWeight = max(300000, MedianOverPrevious100Blocks(BlockWeight)) To (proposed definition) EffectiveMedianBlockWeight = min(max(300000, MedianOverPrevious100Blocks(BlockWeight)), 50*LongTermEffectiveMedianBlockWeight) Notes: 1) There are no other changes to the existing penalty formula, median calculation, fees etc. 2) There is the requirement to store the LongTermBlockWeight of a block unencrypted in the block itself. This is to avoid possible consensus issues over rounding and also to prevent the calculations from becoming unwieldy as we move away from the fork. 3) When the EffectiveMedianBlockWeight cap is reached it is still possible to mine blocks up to 2x the EffectiveMedianBlockWeight by paying the corresponding penalty. Note: the long term block weight is stored in the database, but not in the actual block itself, since it requires recalculating anyway for verification.
* Pruningmoneromooo-monero2019-01-221-0/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The blockchain prunes seven eighths of prunable tx data. This saves about two thirds of the blockchain size, while keeping the node useful as a sync source for an eighth of the blockchain. No other data is currently pruned. There are three ways to prune a blockchain: - run monerod with --prune-blockchain - run "prune_blockchain" in the monerod console - run the monero-blockchain-prune utility The first two will prune in place. Due to how LMDB works, this will not reduce the blockchain size on disk. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. The third way will create a second database, a pruned copy of the original one. Since this is a new file, this one will be smaller than the original one. Once the database is pruned, it will stay pruned as it syncs. That is, there is no need to use --prune-blockchain again, etc.
* blockchain_db: allow getting output keys without commitmentmoneromooo-monero2019-01-161-1/+1
| | | | | Since the commitment has to be calculated for non rct outputs, it slows down a lot unnecessarily if we don't need it
* Merge pull request #4984Riccardo Spagni2019-01-161-1/+2
|\ | | | | | | 008647d7 blockchain_db: speedup tx output gathering (moneromooo-monero)
| * blockchain_db: speedup tx output gatheringmoneromooo-monero2018-12-181-1/+2
| | | | | | | | We know all the data we'll want for getblocks.bin is contiguous
* | Make get_output_key method constmoneroexamples2019-01-071-2/+2
|/ | | | | | get_output_key method is commonly used when working with txs and their key images. Because the method is not const, passing blockchain object though const& or pointers to const is not possible in this context. This is especially problematic in external projects (e.g., projects in moneroexamples) that use monero C++ api to operate on the blockchain and txs. Thus, having get_output_key method will simplify moving blockchain object around through const references and pointers to const objects.
* Merge pull request #4901Riccardo Spagni2018-12-121-0/+7
|\ | | | | | | | | a48f2dab blockchain_prune_known_spent_data: blackball file is now optional (moneromooo-monero) 17b45725 Outputs where all amounts are known spent can now be pruned (moneromooo-monero)
| * Outputs where all amounts are known spent can now be prunedmoneromooo-monero2018-11-271-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Only for pre rct for obvious reasons. Note: DO NOT use a known spent list which includes outputs which are not known spent. If the list includes any output that's just strongly thought to be spent, but not provably so, you risk finding yourself unable to sync past the point where that output is spent. I estimate only 200 MB saved on current mainnet though, unless the new blackballing rule unearths a good amount of large-amount-set extra spent outs.
* | Merge pull request #4854Riccardo Spagni2018-12-041-1/+0
|\ \ | |/ |/| | | bd98e99c Removed a lot of unnecessary includes (Martijn Otto)
| * Removed a lot of unnecessary includesMartijn Otto2018-11-151-1/+0
| |
* | rpc: speedup get_outs.binmoneromooo-monero2018-11-261-2/+2
| |
* | core: avoid unnecessary tx/blob conversionsmoneromooo-monero2018-11-011-1/+1
|/
* blockchain_db: initialize m_hardfork in ctor just in casemoneromooo-monero2018-10-161-1/+1
| | | | Coverity 136568
* v8: per byte fee, pad bulletproofs, fixed 11 ring sizemoneromooo-monero2018-09-111-10/+10
|
* blockchain_db: remove unused get_output_key variantmoneromooo-monero2018-07-301-17/+0
| | | | It was actually incorrect, as it would not return commitment
* Merge pull request #4013luigi11112018-07-191-0/+7
|\ | | | | | | e5592c4 rpc: add blockchain disk size to getinfo (moneromooo-monero)
| * rpc: add blockchain disk size to getinfomoneromooo-monero2018-06-201-0/+7
| | | | | | | | | | This should help new nodes predict how much disk space will be needed for a full sync
* | Merge pull request #3981luigi11112018-07-191-0/+15
|\ \ | | | | | | | | | 45e419b db: store cumulative rct output distribution in the db for speed (moneromooo-monero)
| * | db: store cumulative rct output distribution in the db for speedmoneromooo-monero2018-07-131-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | This gets rid of the temporary precalc cache. Also make the RPC able to send data back in binary or JSON, since there can be a lot of data This bumps the LMDB database format to v3, with migration.
* | | Merge pull request #3854luigi11112018-07-191-0/+14
|\ \ \ | |/ / |/| | | | | | | | | | | | | | 149da42 db_lmdb: enable batch transactions by default (stoffu) 34cb6b4 add --regtest and --fixed-difficulty for regression testing (vicsn) 9e1403e update get_info RPC and bump RPC version (vicsn) 207b66e first new functional tests (vicsn)
generated by cgit v1.2.3 (git 2.51.0) at 2026-08-16 02:50:23 +0000