monzero-core.git/src, branch v0.18.4.4Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.42025-11-12T09:22:38ZMerge pull request #102062025-11-12T09:22:38Ztobtohttob@featherwallet.org2025-11-12T09:22:38Zurn:sha1:516e5355a103a2bf0b7e10328ebcaa2945019445
4e4e343 Daemon: relay empty fluffy block on found block (j-berman)
Daemon: relay empty fluffy block on found block2025-11-12T00:45:06Zj-bermanjustinberman@protonmail.com2025-10-09T18:25:10Zurn:sha1:4e4e3439c9ce5c2adc297fe8b66e69ef0848438ctx pool: only increment m_txpool_weight for newly added pool txs2025-11-12T00:31:37Zj-bermanjustinberman@protonmail.com2025-10-28T00:14:16Zurn:sha1:90dad18bfbe3275142e2f3fe33017cd65486a20f
Otherwise we can end up double counting txs towards the weight,
which can over-state the pool weight. E.g. relay tx to node in
stem phase, add its weight to pool weight, then receive tx
from another node, then bump the pool weight again. That double
counts the tx towards the pool weight.
If the weight exceeds the max, the node will "prune" txs from the
pool. Thus, over-counting is probably a cause of, but perhaps
not the only cause of:
https://github.com/seraphis-migration/monero/issues/148
Merge pull request #101952025-11-11T23:01:13Ztobtohttob@featherwallet.org2025-11-11T23:01:13Zurn:sha1:6f2574d9d2a38a637aff47a59968edec8485c732
26cf4f9 ledger: throw on secret view key export rejection (tobtoht)
Merge pull request #102022025-11-11T22:42:07Ztobtohttob@featherwallet.org2025-11-11T22:42:07Zurn:sha1:68732126e957723d3b7f648447877bf4cab4fc37
dafecd0 cryptonote_protocol: accurate next_needed_height when there is an overlap (0xFFFC0000)
Merge pull request #101992025-11-11T21:52:46Ztobtohttob@featherwallet.org2025-11-11T21:52:46Zurn:sha1:64f230d63adff7b544e8f2ba080ead4b7595ee04
64f2d8e build: prepare v0.18.4.4 (selsta)
ledger: throw on secret view key export rejection2025-11-11T19:57:56Ztobtohttob@featherwallet.org2025-11-11T19:51:52Zurn:sha1:26cf4f914134fa0808ca539e2d0e7d17aac125e1Fix logging deadlock2025-11-11T18:44:26Zj-bermanjustinberman@protonmail.com2025-11-08T00:00:57Zurn:sha1:a83a46d60059a063ec953ba15f4cdcc2b3874440cryptonote_protocol: accurate next_needed_height when there is an overlap2025-11-10T20:58:50Z0xFFFC00000xFFFC0000@proton.me2025-11-05T21:07:25Zurn:sha1:dafecd0addb171751efd31fea417d36da84e5efebuild: prepare v0.18.4.42025-11-10T17:56:57Zselstaselsta@sent.at2025-11-10T17:56:57Zurn:sha1:64f2d8e45dfcdbee8684272946c7c2b844848fa7