Monero v0.18.5.3 backports address restricted RPC, log handling, peer handshakes and database growth. The next release was still being prepared.
1. Monero RPC and database fixes reach the release branch
August 25, 2026 · Watch for a tagged release
Affects monerod restricted RPC, logs, P2P and LMDB.
Four backports landed on release-v0.18. PR #11147 corrects transaction-pool age calculations and hides that age from restricted RPC clients. PR #11149 prevents control characters in JSON input from injecting misleading log output. PR #11157 checks connection state when detecting duplicate handshakes. PR #11159 adjusts database batch estimates to avoid excessive LMDB map growth. These were branch changes, not a new release.
- Wait for a signed release containing the fixes. A merged backport does not establish that an installed binary includes it.
- When upgrading, check restricted RPC responses, peer reconnection and database growth during synchronization.
Sources: Restricted RPC fix · JSON log fix · Handshake fix · Database sizing fix
2. RPC performance rewrite merges into development
August 28, 2026 · Development watch
Affects Block and transaction RPC queries.
PR #10605 reduces repeated transaction parsing, sorting and lookup work in RPC calls. It also allows full mempool transactions to be returned on request. The patch merged into the development branch, not a stable release.
- Test applications that consume transaction-pool responses against a future release before upgrading their production node.
Sources: RPC implementation and review · Release preparation
Monero Research Lab — August 26, 2026
FCMP++ work was approaching another wallet milestone. Developers were finishing hot/cold wallet integration, which separates offline signing from an online wallet. Audit quotes had been requested for the proof circuits, supporting cryptographic code and FCMP++ library. P2Pool work was adding Carrot support ahead of stressnet testing.
The meeting also examined relative time locks for payment channels. These would delay a spend for a fixed period after an earlier transaction. Participants wanted a clearer channel design and discussed how long the delay should be. The feature was still a proposal, with no agreed production rollout. Beta stressnet v3 remained dependent on the wallet work.