11614

Treat the XMR Wallet Fix with Caution | CSV Accounting Discrepancy for Self-Transfers Still at Draft Stage | Around $590, Wait for Confirmation—Don't Chase

Let me make my position clear upfront: this is a user-experience issue worth following, not news that XMR has been upgraded or that its privacy protocol has failed. On October 24, a draft PR numbered 11614 appeared on the Monero project's GitHub. It addresses CSV files exported by the command-line wallet's export_transfers function: when a confirmed transaction sends funds both to an address belonging to the same account and to an external address, cached change from before a rescan may not be included in the amount received by the account owner. As a result, the exported table may overstate spending and understate the cumulative balance. The contributor provided local tests: in a mixed-transfer example, spending is shown as 0.03 before the fix and 0.02 after it. This is only what the PR's test description reports; it does not mean mainnet users have broadly verified the issue.

The status is important and must be clear: the GitHub page marks it as Draft, and it has not been merged. The current GUI and CLI versions on Monero's official download page are still 0.18.5.4. So I won't describe a “proposed CSV accounting fix” as “the wallet has been fixed,” nor exaggerate a CSV reporting discrepancy into a claim that coins have been lost on-chain. For people who actually use XMR for payments and financial reconciliation, reliable transaction-history reporting affects trust and the cost of using the wallet. But a wallet patch awaiting review is not, by itself, an immediate reason to buy. Next, we need to see code review, a merge, backporting, and official release notes. Without all of those steps, we cannot say the fix has reached users.

For the market, I'm watching XMR/USD on Kraken: around $593.70 at the time of writing, with a daily open near $583.71 and a rolling 24-hour range of approximately $562.34 to $605.43. The price is above the daily open but has not broken through the top of the range. That can only be described as relatively strong within a choppy market; this move can't be attributed to a small draft PR. My levels to watch are $590, $605, and $562: if $590 repeatedly fails to hold, the risk-reward for chasing a long position deteriorates; above $605, I want sustained trading confirmation, not just a single spike; if $562 breaks and the price fails to recover, my short-term bullish view is invalidated. Quotes can change, so check the order book again before placing an order.

If I were trading this myself, I wouldn't enter based on the PR alone, and I wouldn't use high leverage. I'd only consider a small spot long: first wait for XMR to hold above $605 and then defend that level on a retest. I'd use no more than 2% of my total capital, entering in two tranches. The first target would be $625; I'd take half off there and protect the rest around my entry price. If the retest falls back below $590, I'd exit rather than wait for $562 to admit I was wrong. If the price simply moves back and forth between $590 and $605, I'd stay out. If it breaks below $562 and fails to reclaim it after two rebound attempts, I'd also close any trial position. These are all conditions for a future plan; I'm not claiming that any trades have already been executed or have made a profit.

Sources: Monero project GitHub PR #11614; Monero official download page. Price reference: live XMR/USD market data on Kraken. #XMR
The above is personal market commentary only and does not constitute investment advice.