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

Age	Commit message (Collapse)	Author	Files	Lines
2022-03-04	Copyright: Update to 2022	mj-xmr	1	-1/+2

2021-02-09	Remove unused variables in monero codebase	Kevin Barbour	1	-3/+0
	There are quite a few variables in the code that are no longer (or perhaps never were) in use. These were discovered by enabling compiler warnings for unused variables and cleaning them up. In most cases where the unused variables were the result of a function call the call was left but the variable assignment removed, unless it was obvious that it was a simple getter with no side effects.
2020-04-01	Hash domain separation	Sarang Noether	1	-5/+4

2020-01-09	ringdb: use a different iv for key and data in rings table	moneromooo-monero	1	-18/+37
	This is technically a record encrypted in two pieces, so the iv needs to be different. Some backward compatibility is added to read data written by existing code, but new data is written with the new code.
2019-08-22	ringdb: fix bug in blackballing	stoffu	1	-1/+1

2019-04-02	simplewallet: new unset_ring command	moneromooo-monero	1	-11/+21
	Useful when debugging, though not much for users
2018-11-15	Removed a lot of unnecessary includes	Martijn Otto	1	-0/+1

2018-10-18	Rename "blackball" for clarity	moneromooo-monero	1	-2/+2
	Apparently some people seem to think it's a censorship list...
2018-09-29	Merge pull request #4407	Riccardo Spagni	1	-7/+8
	43a06350 ringdb: use cursors to be a bit faster (moneromooo-monero)
2018-09-10	record blackballs as amount/offset, and add export ability	moneromooo-monero	1	-19/+27

2018-09-09	ringdb: allow blackballing many outputs at once	moneromooo-monero	1	-38/+57
	It cuts down on txn commits, and speeds up blackballing substantially
2018-04-11	unit_tests: add ringdb unit tests	moneromooo-monero	1	-4/+14

2018-03-16	ringdb: factor ring addition code	moneromooo-monero	1	-22/+16

2018-03-16	ringdb: use the genesis block as a db name	moneromooo-monero	1	-3/+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: add a set_ring command	moneromooo-monero	1	-0/+30
	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-16	wallet: make ringdb an object with database state	moneromooo-monero	1	-125/+98

2018-03-16	wallet: add an output blackball list to avoid using those in rings	moneromooo-monero	1	-6/+114

2018-03-16	wallet: add shared ring database	moneromooo-monero	1	-0/+340
	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.