aboutsummaryrefslogtreecommitdiff
path: root/src/wallet/ringdb.cpp (follow)
AgeCommit message (Collapse)AuthorFilesLines
2020-04-01Hash domain separationSarang Noether1-5/+4
2020-01-09ringdb: use a different iv for key and data in rings tablemoneromooo-monero1-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-22ringdb: fix bug in blackballingstoffu1-1/+1
2019-04-02simplewallet: new unset_ring commandmoneromooo-monero1-11/+21
Useful when debugging, though not much for users
2018-11-15Removed a lot of unnecessary includesMartijn Otto1-0/+1
2018-10-18Rename "blackball" for claritymoneromooo-monero1-2/+2
Apparently some people seem to think it's a censorship list...
2018-09-29Merge pull request #4407Riccardo Spagni1-7/+8
43a06350 ringdb: use cursors to be a bit faster (moneromooo-monero)
2018-09-10record blackballs as amount/offset, and add export abilitymoneromooo-monero1-19/+27
2018-09-09ringdb: allow blackballing many outputs at oncemoneromooo-monero1-38/+57
It cuts down on txn commits, and speeds up blackballing substantially
2018-04-11unit_tests: add ringdb unit testsmoneromooo-monero1-4/+14
2018-03-16ringdb: factor ring addition codemoneromooo-monero1-22/+16
2018-03-16ringdb: use the genesis block as a db namemoneromooo-monero1-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-16wallet: add a set_ring commandmoneromooo-monero1-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-16wallet: make ringdb an object with database statemoneromooo-monero1-125/+98
2018-03-16wallet: add an output blackball list to avoid using those in ringsmoneromooo-monero1-6/+114
2018-03-16wallet: add shared ring databasemoneromooo-monero1-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.