monzero-core.git/src/blockchain_utilities/CMakeLists.txt, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2022-03-04T05:59:20ZCopyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009Update copyright year to 20202020-05-07T02:36:54ZSomaticFanaticafdlkajdlfkj@aldkfjf.com2020-05-07T02:36:54Zurn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6
Update copyright year to 2020
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6Pruning2019-01-22T20:30:51Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-29T22:30:51Zurn:sha1:b750fb27b0f20e9443827732b69a504a76036430
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.
Outputs where all amounts are known spent can now be pruned2018-11-27T15:45:42Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-24T14:49:04Zurn:sha1:17b45725af754a3887f0c59bd5c67c58278d71eb
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 #46942018-11-04T18:47:06ZRiccardo Spagniric@spagni.net2018-11-04T18:47:06Zurn:sha1:68e2efa8f2735558a5ecbfea3f287977b0ad5f4f
a43daebf Add stats utility (Howard Chu)
Merge pull request #45362018-10-26T20:20:39ZRiccardo Spagniric@spagni.net2018-10-26T20:20:39Zurn:sha1:056a58d13fcb87b3eee8937146643e5e193a2790
fd62b6e7 blocks: use auto-generated .c files instead of 'LD -r -b binary' (xiphon)
Add stats utility2018-10-23T18:43:31ZHoward Chuhyc@symas.com2018-10-22T16:31:48Zurn:sha1:a43daebf57560aef4e83b3cce7e92bab3f2070dc
Report statistics from a blockchain DB
blocks: use auto-generated .c files instead of 'LD -r -b binary'2018-10-21T22:12:00Zxiphonxiphon@protonmail.com2018-10-09T12:33:39Zurn:sha1:fd62b6e79f87503bf27a3c8709aaf9cc4ae36146Rename "blackball" for clarity2018-10-18T18:45:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-18T18:05:51Zurn:sha1:99cd6f961a15d5a16668be44c200b5f78024e618
Apparently some people seem to think it's a censorship list...