monero.git - Monero: the secure, private, untraceable cryptocurrency

Age	Commit message (Collapse)	Author	Files	Lines
2018-08-15	Merge pull request #4196	luigi1111	1	-4/+3
	361513a blockchain_blackball: use a bit less memory (moneromooo-monero)
2018-08-09	blockchain_blackball: use a bit less memory	moneromooo-monero	1	-4/+3

2018-07-30	blockchain_blackball: allow resumable interrupt with ^C	moneromooo-monero	1	-0/+13

2018-06-20	Merge pull request #3924	luigi1111	1	-1/+1
	afed978 Fixes #3645: error on freebsd lambda return values forced to std::string (rockhouse)
2018-06-04	Fixes #3645: error on freebsd lambda return values forced to std::string	S	1	-1/+1

2018-05-30	blockchain_blackball: also blackball N N-sized duplicate rings	moneromooo-monero	1	-5/+48
	These are unlikely to happen at random, but Wijaya et al made a paper about it, so people might try it on purpose now (and it turns out it's easy to add anyway)
2018-05-30	blockchain_blackball: add incremental mode	moneromooo-monero	1	-19/+102

2018-04-12	blockchain_blackball: fix build with CLANG 5	moneromooo-monero	1	-1/+2
	It doesn't like the explicit NULL dereference (which is fine, honest)
2018-03-16	ringdb: use the genesis block as a db name	moneromooo-monero	1	-1/+3
	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-16	wallet: make ringdb an object with database state	moneromooo-monero	1	-4/+6

2018-03-16	blockchain_utilities: new blockchain_blackball tool	moneromooo-monero	1	-0/+423
	It scans for known spent outputs and stores their public keys in a database which can then be read by the wallet, which can then avoid using those as fake outs in new transactions. Usage: monero-blockchain-blackball db1 db2... This uses the shared database in ~/.shared-ringdb