aboutsummaryrefslogtreecommitdiff
path: root/src/common/pruning.h (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2019-01-22Pruningmoneromooo-monero1-30/+15
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.
2018-09-10record blackballs as amount/offset, and add export abilitymoneromooo-monero1-5/+5
2018-09-09ringdb: allow blackballing many outputs at oncemoneromooo-monero1-1/+2
It cuts down on txn commits, and speeds up blackballing substantially
2018-04-11unit_tests: add ringdb unit testsmoneromooo-monero1-0/+1
2018-03-16ringdb: use the genesis block as a db namemoneromooo-monero1-1/+1
This will avoid careless forkers polluting the shared database even if they make their own chain. They'll then automatically start using another subdb, and any key-reusing fork of those forks will reuse their subdbs.
2018-03-16wallet: add a set_ring commandmoneromooo-monero1-0/+1
This is so one can set rings for spent key images in case the attackers don't merge the ring matching patch set.
2018-03-16wallet: make ringdb an object with database statemoneromooo-monero1-9/+23
2018-03-16wallet: add an output blackball list to avoid using those in ringsmoneromooo-monero1-0/+5
2018-03-16wallet: add shared ring databasemoneromooo-monero1-14/+10
This maps key images to rings, so that different forks can reuse the rings by key image. This avoids revealing the real inputs like would happen if two forks spent the same outputs with different rings. This database is meant to be shared with all Monero forks which don't bother making a new chain, putting users' privacy at risk in the process. It is placed in a shared data directory by default ($HOME/.shared-ringdb on UNIX like systems). You may use --shared-ringdb-dir to override this location, and should then do so for all Monero forks for them to share the database.
2018-01-26Update 2018 copyrightxmr-eric1-1/+1
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni1-1/+1
2017-02-08extract some basic code from libcryptonote_core into libcryptonote_basickenshi841-1/+1
2015-12-31updated copyright yearRiccardo Spagni1-1/+1
2015-01-02year updated in licenseRiccardo Spagni1-1/+1
2014-07-23License updated to BSD 3-clausefluffypony1-3/+29
2014-03-03moved all stuff to githubAntonio Juarez1-0/+23