Monero (XMR) Blockchain v6.1.5

Release Date: August 11, 2026 Tags: PERFORMANCE, WALLETS, DATABASE, MONERO, XMR, ECOSYSTEM

Overview

A performance release, all of it in the work the addon does while nothing else is happening.

A Monero wallet that nobody opens falls behind the chain, so whenever no deposit check and no withdrawal is in flight the addon quietly re-syncs one dormant wallet. On an idle installation it was making that choice every two seconds, and doing the full amount of work each time, to answer a question whose bar is six hours.

The database now does the filtering, the shortlist is held for a minute instead of rebuilt on each pass, and a refresh that is still running is no longer asked for again while it finishes. No balance, deposit or withdrawal is touched, and no figure moves — there is nothing to re-check after updating.

Requires Core v6.6.3.

Update Instructions

pnpm updator

Nothing to configure. No setting changes and no data repair.

Changed

Choosing which dormant wallet to refresh

• Changed the search for the next wallet to re-sync so the database returns only wallets holding a balance. It previously read every ecosystem wallet on the installation, on every chain and at any balance, and threw away the ones it could not use — thirty times a minute, and on installations that hold no Monero wallet at all.
• Changed the shortlist of Monero wallets to be held for one minute rather than rebuilt on every pass, so each stored address is unpacked once a minute instead of thirty times. A wallet that is already a candidate is chosen either way, because a wallet only becomes one six hours after its last sync.
• A wallet that has just become a candidate — a newly created one, or one whose balance has only now gone positive — can wait up to a minute longer for its first background sync. Nothing else waits on that sync: deposits and withdrawals open the wallet themselves.

Starting a refresh that is already under way

Re-syncing a dormant wallet opens it against your wallet RPC and can take minutes, and the idle loop deliberately does not wait for it — waiting would stop the loop watching for real deposits. Nothing stopped the loop deciding afresh two seconds later, so a second refresh was queued behind the one already in progress. A wallet does not count as synced until its sync finishes, so if it was still the one longest overdue it was chosen again — opened and re-synced twice over, with your daemon carrying the second pass for nothing.

• Changed the idle loop to run one background refresh at a time. It still never waits on the refresh, so it keeps watching for deposits the whole time one runs.