monzero-core.git/src/cryptonote_core/tx_pool.h, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2026-05-08T15:40:38Zzmq: apply restricted-mode privacy filtering to get_transaction_pool2026-05-08T15:40:38Zgreatjourney589wangkyle589@gmail.com2026-05-08T15:33:34Zurn:sha1:878c781764e62d8616ae49a42baf05366a1d7336
Add an include_sensitive parameter to tx_memory_pool::get_pool_for_rpc
(and its core passthrough), mirroring the include_sensitive_data
parameter on the HTTP analog get_transactions_and_spent_keys_info.
When false, receive_time and last_relayed_time are zeroed using the
same masking already applied on the HTTP path.
The ZMQ handler in daemon_handler.cpp passes !m_restricted, so
--restricted-zmq-rpc callers now receive the same privacy-filtered view
as restricted HTTP callers instead of the unfiltered timing metadata
they previously got. Stem-phase txs continue to be excluded regardless
(relay_category::broadcasted filter unchanged).
Refs #10529.
Fix ZMQ-PUB reporting of mempool txes that were initially in stem phase2026-04-24T13:19:51ZLee Clagettcode@leeclagett.com2026-03-06T20:55:26Zurn:sha1:73f1eaaed6defa6fc25fc7e74b51679e365cb7e5tx_memory_pool: speedup get_complement() for large requests2026-03-22T09:50:10Zjeffro256jeffro256@tutanota.com2025-11-03T23:05:57Zurn:sha1:0761024b349048ebf79dbfe71caab11826833464
Changes complexity from M*N to (2*N+M)*log2(M). The FCMP++ stressnet recently hit mempool sizes of ~55k txs.
If the requesting node's mempool is populated, this results in an average of (55000*55000)/2
(about 1.5 billion) comparisons for the responding node. Under this commit, this would be reduced to
(55000+55000)*log2(55000) comparisons (about 2.6 million), a 99.83% reduction.
blockchain sync: reduce disk writes from 2 to 1 per tx2025-03-10T06:32:08Zjeffro256jeffro256@tutanota.com2024-01-17T23:17:16Zurn:sha1:008ba966da88f073f226b299533faca905ceabf8Fixed mempool pruning2024-03-08T20:03:41ZSChernykh15806605+SChernykh@users.noreply.github.com2024-03-08T19:58:21Zurn:sha1:b5b72ae05c5b47b76e57d565de0bac5706530c6a
- Fixed undefined behavior after a call to `remove_tx_from_transient_lists` (it used an invalid iterator)
- Fixed `txCompare` (it wasn't strictly weak ordered)
Enforce restricted # pool txs served via RPC + optimize chunked reqs [release-v0.18]2023-07-09T06:38:18Zj-bermanjustinberman@protonmail.com2022-12-14T00:08:56Zurn:sha1:f137a35984985232a3aae50cd4c7b47634866594
- `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when
returning pool txs via a restricted RPC daemon.
- A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs
in the `added_pool_txs` field, and returns any remaining pool hashes
in the `remaining_added_pool_txids` field. The client then requests
the remaining txs via `/gettransactions` in chunks.
- `/gettransactions` no longer does expensive no-ops for ALL pool txs
if the client requests a subset of pool txs. Instead it searches for
the txs the client explicitly requests.
- Reset `m_pool_info_query_time` when a user:
(1) rescans the chain (so the wallet re-requests the whole pool)
(2) changes the daemon their wallets points to (a new daemon would
have a different view of the pool)
- `/getblocks.bin` respects the `req.prune` field when returning
pool txs.
- Pool extension fields in response to `/getblocks.bin` are optional
with default 0'd values.
wallet2, RPC: Optimize RPC calls for periodic refresh from 3 down to 1 call [release-v0.18]2023-07-09T06:30:53Zrbrunner7rbrunner@dreamshare.ch2021-11-21T16:40:50Zurn:sha1:23f782b21113035b57e4560d6a9b522ac1f03ccaMerge pull request #84672022-08-09T22:43:32Zluigi1111luigi1111w@gmail.com2022-08-09T22:43:32Zurn:sha1:b9e8504cfb0cc539abf1d27057ff567df86d2e37
fac7c43 continue pool pruning even if a tx can't be found (j-berman)
Merge pull request #84552022-08-09T01:29:56Zluigi1111luigi1111w@gmail.com2022-08-09T01:29:56Zurn:sha1:5c33f40cd8b75ad6f486fa1738df1f3462ca1ac1
099fc1f Fixed get_block_template_backlog performance (SChernykh)
continue pool pruning even if a tx can't be found2022-07-27T00:28:02Zj-bermanjustinberman@protonmail.com2022-07-01T15:30:49Zurn:sha1:fac7c4364427eacbf513ae7ab813179995722920