10 Commits (43a06350cf9a14d6a86bd08898bad15c19a0272d)

Author	SHA1	Message	Date
moneromooo-monero	43a06350cf	ringdb: use cursors to be a bit faster	6 years ago
moneromooo-monero	44439c3208	record blackballs as amount/offset, and add export ability	6 years ago
moneromooo-monero	50cb370d5b	ringdb: allow blackballing many outputs at once ... It cuts down on txn commits, and speeds up blackballing substantially	6 years ago
moneromooo-monero	6a61f520e2	unit_tests: add ringdb unit tests	6 years ago
moneromooo-monero	d32ef7b0f2	ringdb: factor ring addition code	6 years ago
moneromooo-monero	504428ab4a	ringdb: use the genesis block as a db name ... 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.	6 years ago
moneromooo-monero	b09e5181cc	wallet: add a set_ring command ... This is so one can set rings for spent key images in case the attackers don't merge the ring matching patch set.	6 years ago
moneromooo-monero	db10dd6d83	wallet: make ringdb an object with database state	6 years ago
moneromooo-monero	d29ea0455a	wallet: add an output blackball list to avoid using those in rings	6 years ago
moneromooo-monero	5f146873c5	wallet: add shared ring database ... 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.	6 years ago