Monero Blockchain 6.1.8

Latest

4 September 2026

DEPOSITSLOCKED-FUNDSMONEROXMR

Monero (XMR) Blockchain v6.1.8

Release Date: September 4, 2026 Tags: DEPOSITS, LOCKED-FUNDS, MONERO, XMR

Overview

A transfer that is confirmed but still locked is not a deposit yet, and the monitor now knows it. A Monero sender can attach an unlock_time to a transfer, and the daemon then refuses to spend those outputs until that height or time is reached, however many confirmations they carry. The monitor read only the confirmation count, so such a transfer was credited at six confirmations, the customer could trade or transfer the balance at once, and the platform held coins it could not move until the sender's chosen unlock.

Requires Core v6.7.6 and Ecosystem v6.5.0, which carry the shared outcome-classification helpers this addon now imports.

Update Instructions

# 1. Update the addon in Admin → System → Extensions
# 2. Restart the backend
pnpm updator

No schema change, no seeder, no .env change. Update Core and Ecosystem in the same window.

Fixed

  • Fixed — a deposit is credited only when it is spendable: six confirmations and the wallet RPC no longer reports it locked, with its unlock_time reached. A confirmed-but-locked transfer keeps the monitor polling and is credited when the lock clears; the deposit page shows it as pending until then. The same rule is applied at every point the addon reads a transfer's status, including the background scan.

Changed

A send for the platform's own movements

  • ChangedsendXmrFromWallet: a queued send from one wallet file that opens with a refresh, probes the fee, checks the remaining balance against a floor inside the open, relays exactly once and closes — for Core 6.7.6's pool-backing engine, from the treasury's wallet or master_wallet. Also getWalletBalances, the per-wallet balance read the Ecosystem settlement mover's source checks make before a Monero leg is sent (the treasury's or the master wallet's unlocked balance); it throws on an outage instead of answering zero. Core's custody reads do not use it. transferXMR and handleMoneroWithdrawal are unchanged. Requires Core 6.7.6 and Ecosystem 6.5.0.