monzero-core.git/src/rpc/daemon_handler.cpp, branch v0.18.5.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.5.12026-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.
zmq: add restricted checks to GetInfo2026-04-29T17:05:35Zselstaselsta@sent.at2026-04-29T16:54:14Zurn:sha1:f31bb18174950237ea6ed083614c37a04d33b46ezmq: add missing restricted rpc check for get_block_headers_by_height2026-04-27T15:58:43ZJeetrajjeetrajsinh2005@gmail.com2026-04-26T20:48:40Zurn:sha1:a4efa1585e15b0f2fc54bc466e95fe7161788eb7zmq: add more missing restricted rpc checks2026-04-24T15:35:54Zselstaselsta@sent.at2026-04-19T22:06:29Zurn:sha1:6e51bdcd8ef233814d81c2b953fa82f13cbbd442zmq: add missing restricted rpc check2026-04-18T15:38:26Zselstaselsta@sent.at2026-04-18T15:36:21Zurn:sha1:e6ce535b24c48104fb1cfebc1ae03686afe820f2zmq: add restricted rpc mode2026-04-01T16:06:10Zselstaselsta@sent.at2026-03-25T19:37:18Zurn:sha1:7f2cfe9294ec1fa7bece2a8069114c1b6985650fAdd new dynamic fees to ZMQ2025-06-13T21:27:36ZLee Clagettcode@leeclagett.com2025-06-13T21:10:17Zurn:sha1:9002681c1ef192bbdddcb1c5f49eac1b647af207blockchain sync: reduce disk writes from 2 to 1 per tx2025-03-10T06:32:08Zjeffro256jeffro256@tutanota.com2024-01-17T23:17:16Zurn:sha1:008ba966da88f073f226b299533faca905ceabf8Fix ZMQ DaemonInfo:2024-06-25T00:06:33ZLee *!* Clagettcode@leeclagett.com2024-06-24T23:57:20Zurn:sha1:c5ad937cc11d3181b7549db573ac37ec635be96e
* top_block_hash was never set in handler
* wide_difficulty was never sent in JSON
* wide_cumulative_difficulty was never sent in JSON
Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]2024-04-29T05:08:53Zjeffro256jeffro256@tutanota.com2024-02-04T03:59:58Zurn:sha1:dd47d03cf2b5b3dc59cd99aca247d1025679f83a
Related to https://github.com/monero-project/research-lab/issues/78
Added a relay rule that enforces the `unlock_time` field is equal to 0 for non-coinbase transactions.
UIs changed:
* Removed `locked_transfer` and `locked_sweep_all` commands from `monero-wallet-cli`
APIs changed:
* Removed `unlock_time` parameters from `wallet2` transfer methods
* Wallet RPC transfer endpoints send error codes when requested unlock time is not 0
* Removed `unlock_time` parameters from `construct_tx*` cryptonote core functions
@tobtoht: undo rebase changes tx.dsts -> tx_dsts