Monero (XMR) Blockchain v6.2.3

Release Date: October 13, 2026 Tags: DEPOSITS, MONERO, XMR, WALLET-RPC, DORMANT WALLETS

Overview

A Monero deposit to a member who was away was credited only after they came back. Their wallet was opened by the background pass that keeps dormant wallets up to date, which refreshed it and closed it without crediting anything, and which skipped wallets holding nothing, so a first deposit to one was never seen. On one live install a 0.01 XMR deposit that wallet-rpc had logged at 19:43 was credited 13 hours later, after the owner signed in. The pass now looks at every Monero wallet and credits what it finds.

Three smaller fixes: a wallet that cannot be opened no longer keeps the pass from the wallets after it, a wallet-rpc started without the daemon login stops costing a failed refresh per wallet, and the deposit page counts to 10 for a transfer that has to reach 10 confirmations.

No new requirement: Core v6.7.9 and Ecosystem v6.5.3, as before.

Update Instructions

pnpm updator

No schema change, no seeder, no .env change. The backend and the cron process restart at the end.

Upgrade Notes

Start monero-wallet-rpc with the daemon login

• If monero-wallet-rpc is launched with --daemon-address but without --daemon-login in front of a monerod that requires one, add --daemon-login <XMR_RPC_USER>:<XMR_RPC_PASSWORD> to the launch command and restart wallet-rpc. The log now says so once per process, as a warning from XMR. Until you do, the platform points each opened wallet at the daemon before refreshing it. That works, but it costs one extra call and one info line, "wallet-rpc daemon set to host:port (authenticated)", on every open.

The dormant pass is slow on purpose

• The pass opens one wallet at a time, no more often than every 3 minutes, and the first one 3 minutes after the process starts, so a full lap takes at least 3 minutes times the number of Monero wallets. It runs only where the cron jobs run, only while nothing is being watched live, and not when Rust owns Monero.
• A deposit is credited by the first pass that sees it spendable. Monero needs 10 confirmations before a deposit can be spent.
• A wallet the pass could not open (its wallet file is missing, or the file answers as another address) is tried again after 30 minutes instead of at every turn. The open error is in the log each time.

Fixed

Dormant Monero wallets credit their deposits

A member the deposit scanner no longer watches had their wallet opened only by the cron's dormant refresh. By default that is 72 hours after they last opened their Monero wallet or the deposit page: Monero is kept off the passive login lane unless ECOSYSTEM_SCAN_PASSIVE_SKIP_CHAINS says otherwise. The pass refreshed the wallet and closed it, so a deposit it found was credited when the member next signed in.

• Fixed the pass to take every ECO Monero wallet that has a recorded address. It scans the one this process has gone longest without refreshing (a wallet not refreshed in 30 minutes counts as dormant, and after a restart every wallet is "never"), and it credits the spendable deposits it finds after the session, by the same proof the deposit scanner uses.
• Fixed the pass skipping wallets that held nothing, which hid a first deposit.
• Fixed the pass getting stuck on a wallet that cannot be opened. A recorded address with no wallet file behind it never completes a refresh, so it stayed "never refreshed" and, once every other wallet had been refreshed once, it was the stalest on every turn: the wallets after it were not reached again. The pass now remembers when it last tried each wallet and leaves a wallet it tried alone for 30 minutes, whatever came of it. A refresh that never reached the wallet (wallet-rpc busy, a live deposit check running) does not count as a try.
• The log shows "Background scan: scanning dormant wallet …", "… scanned, N new deposit(s)" and "Background scan credited deposit … for wallet …".

A wallet-rpc started without the daemon login

monero-wallet-rpc gives every wallet it opens the daemon settings it was launched with. Started without --daemon-login in front of a monerod that requires one, every session's first refresh failed with error -38 and was rescued by pointing the wallet at the daemon: a warning and a wasted call per wallet in both the web and the cron process.

• Fixed it: after a refresh failed in that way and was rescued, each opened wallet is pointed at the daemon before its refresh. The same flag is set by any daemon-class failure that a retry cures (error -9, "daemon is busy", "Failed to connect"), so a monerod hiccup on a correctly launched wallet-rpc sets it for the rest of that process. A restart starts again from the beginning.

The deposit page stopped counting at 5 of 6

• Fixed the pending deposit frame. Monero credits a deposit only at its 10-block spendable age, but the frame said 6 confirmations were required and sent 7, and the log printed "7/6". The deposit page stopped updating at its last count. While the wallet reports the transfer as locked and it has 6 or more confirmations, the frame now says /10, so the page counts 6/10 up to 9/10.