monzero-core.git/src/blockchain_db/blockchain_db.h, branch v0.12.4.0 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.12.4.0 2018-07-03T10:17:48Z tx_pool: initialize bitflags padding since it gets written to storage 2018-07-03T10:17:48Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-06-05T18:59:45Z urn:sha1:4e2b279a940e09fd90525f3afa91176ff40b7c6b Avoids valgrind reporting uninitialized data usage speed up get_output_distribution (and precalc common case) 2018-05-19T12:28:02Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-05-16T21:41:50Z urn:sha1:ffe9d8821af608168b65bb6c6c881dcae0913e33 speedup get_output_histogram for all amounts when min_count > 0 2018-04-22T21:36:01Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-03-22T17:51:58Z urn:sha1:d003f07c59933725b7e35ca758bbfdb2b11b4ea3 This skips the vast majority of "dust" output amounts with just one instance on the chain. Clocks in at 0.15% of the original time on testnet. add RPC to get a histogram of outputs of a given amount 2018-03-16T10:32:26Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-02-19T11:15:15Z urn:sha1:41f727ce42d0fce9e40e4da7bf4abda92eef1016 blockchain_db: initialize m_open in base class ctor 2018-02-02T15:21:39Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-02-02T15:21:39Z urn:sha1:ad11db9144f766d86d4aa4904eecd446fb670597 It's cleaner this way, since it's a base class field Coverity 136568 Update 2018 copyright 2018-01-26T15:03:20Z xmr-eric eric@moneroeric.com 2018-01-07T05:05:16Z urn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880 Fix exceptions not finding txpool txes when relaying 2017-12-20T13:02:53Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-12-14T17:09:30Z urn:sha1:ae8602303a0285abd28c044309a8456c748b34a3 move includes around to lessen overall load 2017-12-16T22:46:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-11-25T22:25:05Z urn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341 Merge pull request #2615 2017-11-14T12:53:10Z Riccardo Spagni ric@spagni.net 2017-11-14T12:53:10Z urn:sha1:fd0740e5e7d53e4cf2f7c03501c111545e30836a 10013e94 Protect node privacy by proper filtering in restricted-mode RPC answers (binaryFate) Protect node privacy by proper filtering in restricted-mode RPC answers 2017-11-08T12:07:07Z binaryFate binaryfate@users.noreply.github.com 2017-11-08T12:06:41Z urn:sha1:10013e94342c0d9ca2f10c79779b08affc5209c1 This patch allows to filter out sensitive information for queries that rely on the pool state, when running in restricted mode. This filtering is only applied to data sent back to RPC queries. Results of inline commands typed locally in the daemon are not affected. In practice, when running with `--restricted-rpc`: * get_transaction_pool will list relayed transactions with the fields "last relayed time" and "received time" set to zero. * get_transaction_pool will not list transaction that have do_not_relay set to true, and will not list key images that are used only for such transactions * get_transaction_pool_hashes.bin will not list such transaction * get_transaction_pool_stats will not count such transactions in any of the aggregated values that are computed The implementation does not make filtering the default, so developers should be mindful of this if they add new RPC functionality. Fixes #2590.