monzero-core.git/src/blockchain_db/blockchain_db.h, branch crash-plMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=crash-pl2018-03-16T10:32:26Zadd RPC to get a histogram of outputs of a given amount2018-03-16T10:32:26Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-19T11:15:15Zurn:sha1:41f727ce42d0fce9e40e4da7bf4abda92eef1016blockchain_db: initialize m_open in base class ctor2018-02-02T15:21:39Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-02T15:21:39Zurn:sha1:ad11db9144f766d86d4aa4904eecd446fb670597
It's cleaner this way, since it's a base class field
Coverity 136568
Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880Fix exceptions not finding txpool txes when relaying2017-12-20T13:02:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-12-14T17:09:30Zurn:sha1:ae8602303a0285abd28c044309a8456c748b34a3move includes around to lessen overall load2017-12-16T22:46:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-11-25T22:25:05Zurn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341Merge pull request #26152017-11-14T12:53:10ZRiccardo Spagniric@spagni.net2017-11-14T12:53:10Zurn: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 answers2017-11-08T12:07:07ZbinaryFatebinaryfate@users.noreply.github.com2017-11-08T12:06:41Zurn: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.
track double spending in the txpool2017-11-06T00:05:44Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-22T12:57:20Zurn:sha1:ccf53a566c1c2e980ed30a7371b8789ffb4c01a7
Transactions in the txpool are marked when another transaction
is seen double spending one or more of its inputs.
This is then exposed wherever appropriate.
Note that being marked with this "double spend seen" flag does
NOT mean this transaction IS a double spend and will never be
mined: it just means that the network has seen at least another
transaction spending at least one of the same inputs, so care
should be taken to wait for a few confirmations before acting
upon that transaction (ie, mostly of use for merchants wanting
to accept unconfirmed transactions).
Use actual batch size for resize estimates2017-09-17T21:08:40ZHoward Chuhyc@symas.com2017-09-16T23:12:42Zurn:sha1:d2d8a41c47b408df35d1379255fc009f50a0b770
And optimize import startup:
Remember start_height position during initial count_blocks pass
to avoid having to reread entire file again to arrive at start_height
move db specific options to BlockchainDB2017-08-29T10:43:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-29T10:14:42Zurn:sha1:a95e460c7116589b5dedf5c966cb84893fe8d521
Avoids common depending on blockchain_db, which can cause
link errors.