monzero-core.git/src/cryptonote_core/tx_pool.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-02-07T13:42:12Ztx_pool: add a max pool size, settable with --max-txpool-size2018-02-07T13:42:12Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-01-29T21:20:24Zurn:sha1:bc61ae69bfb20d2bdfa3d3716691e316bdbb6cb5Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880Merge 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).
json serialization for rpc-relevant monero types2017-09-05T16:20:27ZThomas Wingettewinget@gmail.com2017-09-05T16:20:27Zurn:sha1:77986023c37737e298fc7c3e9938cce0e10d8b80
Structured {de-,}serialization methods for (many new) types
which are used for requests or responses in the RPC.
New types include RPC requests and responses, and structs which compose
types within those.
# Conflicts:
# src/cryptonote_core/blockchain.cpp
rpc: add a new RPC to get current txpool backlog (sizes and fees)2017-08-26T15:23:31Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-08-26T15:23:31Zurn:sha1:55bec1f03db039e03bfccec24c88ff08b15b6381tx_pool: remove obsolete unused m_config_folder field2017-07-30T11:03:43Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-07-30T11:03:43Zurn:sha1:14ec6ed80d488a3ab80b2d949202a1d9fe94d84cSpeedup print_pool_stats2017-06-01T16:34:03ZHoward Chuhyc@symas.com2017-05-31T18:11:56Zurn:sha1:5414970dcd05e77a8734f142969c1c805f056f52
Since we're just counting txs, there's no reason to deserialize all the blobs.
Merge pull request #19822017-05-30T19:12:44ZRiccardo Spagniric@spagni.net2017-05-30T19:12:44Zurn:sha1:545e2b003c6a4930e9f18e6d5696c2cd85a5cb22
b52abd13 Move txpool to the database (moneromooo-monero)