monzero-core.git/src/cryptonote_core, 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-06-30T10:03:46ZMerge pull request #107792026-06-30T10:03:46Ztobtohttob@featherwallet.org2026-06-30T10:03:46Zurn:sha1:4f92268d7c16741cfb41e5bbe2aa46cc260a9ea5
d67a8d8 build: prepare v0.18.5.1 (selsta)
ACKs: SNeedlewoods, plowsof
build: prepare v0.18.5.12026-06-29T16:02:00Zselstaselsta@sent.at2026-06-15T12:33:13Zurn:sha1:d67a8d8e9d9dd99147e715ce7fb5887c2dd69f2eblockchain: improve incoming block scan table handling2026-06-29T12:08:49Zselstaselsta@sent.at2026-06-29T12:07:28Zurn:sha1:05426c36cf6f77a7b0f9bcb0f46a0fd5219f6fa4Merge pull request #107182026-06-10T17:14:27Ztobtohttob@featherwallet.org2026-06-10T17:14:27Zurn:sha1:4f8835d51e5a011c48035348f1b42a908363e6cd
2de5e82 Fix: check hwdev.generate_output_ephemeral_keys result (SChernykh)
Merge pull request #105432026-06-09T18:00:03Ztobtohttob@featherwallet.org2026-06-09T18:00:03Zurn:sha1:70d57adc4b08c39e391468369f1a29a532fb9a8e
878c781 zmq: apply restricted-mode privacy filtering to get_transaction_pool (greatjourney589)
Merge pull request #107152026-06-09T17:54:27Ztobtohttob@featherwallet.org2026-06-09T17:54:27Zurn:sha1:c6e5759f31a3d37be86f1da762401cc9d1ba7c7f
3d856f4 Blockchain: fix wrong block_weight in handle_get_objects (SChernykh)
Fix: check hwdev.generate_output_ephemeral_keys result2026-06-04T08:04:29ZSChernykh15806605+SChernykh@users.noreply.github.com2026-06-04T08:03:15Zurn:sha1:2de5e8227f356c31784e249ca5317e7faf4ba969
If it fails, out_eph_public_key and view_tag remain uninitialized.
Blockchain: fix wrong block_weight in handle_get_objects2026-06-04T05:40:07ZSChernykh15806605+SChernykh@users.noreply.github.com2026-06-04T05:37:53Zurn:sha1:3d856f4825283e66a7ebbe9ac32e3f864bc906e2
- When there are missing IDs, blocks.size() != arg.blocks.size(), so arg.blocks can't be indexed by `i` - the indices will be wrong, the wrong weight will be returned to some peer and this peer will ban our node.
Use `bl.second` instead of `arg.blocks[i]`. Also it saves one DB query per returned block.
tx_pool: fix use-after-free in prune()2026-06-03T18:49:42ZSChernykh15806605+SChernykh@users.noreply.github.com2026-06-03T18:47:05Zurn:sha1:ab6a1c8a3da2b252599fcb72c16f26fa56ba4cc8
- txid was a reference to an item which was later deleted in remove_tx_from_transient_lists(), and txid was used after that
zmq: 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.