From 17b45725af754a3887f0c59bd5c67c58278d71eb Mon Sep 17 00:00:00 2001 From: moneromooo-monero Date: Sat, 24 Nov 2018 14:49:04 +0000 Subject: Outputs where all amounts are known spent can now be pruned 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. --- src/blockchain_db/lmdb/db_lmdb.h | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/blockchain_db/lmdb/db_lmdb.h') diff --git a/src/blockchain_db/lmdb/db_lmdb.h b/src/blockchain_db/lmdb/db_lmdb.h index 26159ab4d..6db241240 100644 --- a/src/blockchain_db/lmdb/db_lmdb.h +++ b/src/blockchain_db/lmdb/db_lmdb.h @@ -345,6 +345,8 @@ private: void remove_output(const uint64_t amount, const uint64_t& out_index); + virtual void prune_outputs(uint64_t amount); + virtual void add_spent_key(const crypto::key_image& k_image); virtual void remove_spent_key(const crypto::key_image& k_image); -- cgit v1.2.3