11655

XMR at around $601 | Wallet transaction-proof changes still under review | I assess privacy and proof separately

I’m taking a wait-and-see approach. What’s more worth watching today are two specific changes to Monero wallet software, rather than treating the term “privacy coin” as a guarantee that information can never be exposed. On October 31, the Monero official code repository proposed PR #11655: developers suggest that wallets refuse to generate a certain type of incoming-payment proof for transactions they have sent, because in certain circumstances the proof could also reveal information related to change. The page shows that one reviewer has approved it, but the PR remains open. Another PR, #11654, aims to fix an issue where proofs for older v1 transactions fail to generate or verify when reading pruned data. The proposed solution is to fetch the full transaction only for v1 and check its transaction hash. That PR has not been merged either. Both are code proposals, not mainnet upgrades that have already gone live, and they do not justify concluding that privacy has failed for all XMR transactions.

Why should the market care about transaction proofs? In some cases, people need to prove a payment to a recipient, reconcile merchant accounts, or resolve disputes. Whether proof features work reliably and what they might reveal are part of the wallet security experience. Privacy protections and the option to provide proof must be assessed together. But a PR being reviewed does not automatically change the circulating supply, fees, or exchange listing policies. I’ll watch for four milestones: the merge, an official release, regression tests, and an official explanation. The latest stable core software listed on Monero’s website is still version 0.18.5.4, released on October 16; its release notes describe it as a minor fix. The FATF’s previously published targeted review of virtual asset service providers also did not name XMR or issue a ban against it, so regulatory discussion should not be used to exaggerate a development PR into a sweeping ban.

The market reaction remains range-bound. At the time of writing, XMR/USD was around $601 on Kraken, with a 24-hour range of roughly $590.6 to $609.9. The $610 level is nearby resistance; only a sustained hold above it could open the way to $620. To the downside, $590 comes first, followed by $580. My view is that wallet security discussions matter over the long term, but they are not enough on their own to spark a chase for gains today. If the PR is withdrawn or the official release differs from the current description, I would revise my technical assessment. If the price falls below $590 and liquidity deteriorates noticeably on major trading venues, the short-term recovery thesis is invalidated. If the price holds above $610 and the change is officially merged with clear guidance for users, I’ll reassess whether the risk has decreased. Don’t mistake a reviewer’s “approval” of a code change for an official release.

If I were trading myself, I would stay out for now and wait for direction, with 0% in additional spot positions and 0% in leveraged positions. I would only consider a long position of up to 2% of total capital if XMR closes above $610 for two consecutive one-hour candles, holds above $606 on a retest, and liquidity and spreads remain normal. The first target would be $620, where I’d take half off; I’d let the rest run toward $632. I’d set a stop below $596 and close the entire position if the one-hour candle closes below $590. If the price falls below $590 first, I would not chase a short while liquidity is thinning; I’d wait for a new base and further project-related facts. Conditions that have not been triggered are just a plan, not a record of trades.

#XMR
This is my personal market observation only and does not constitute investment advice.

XMR’s privacy boundaries face renewed scrutiny｜Transaction-proof fix still under review｜I’m not chasing security narratives

My stance is cautious observation, especially because a code review should not be described as a vulnerability already fixed or a mainnet incident. On October 31, a proposal to modify the wallet appeared in the Monero official code repository as PR #11655. The author wants the wallet to refuse to generate a certain type of payment proof (InProof) for the wallet’s own address in transactions sent by the wallet itself. The proposal explains that in certain cases where someone sends funds to themselves, the relevant proof could reveal more transaction information than the holder originally intended to share. The page currently shows the PR as still Open. Although one reviewer has expressed approval, there is no evidence that it has been merged, officially released, or enabled network-wide. The author also explicitly lists other proof pathways not covered by this change, so it cannot be summed up as “the privacy issue is fully resolved.” The latest official GUI version currently visible on the website remains version 0.18.5.4, released on October 16.

What does this have to do with XMR transactions? Monero’s privacy is not a switch; its boundaries are shaped by default on-chain protections, wallet operations, and proofs that users choose to share. A payment proof is information provided to a specific person to verify a transaction. Using it improperly can change what the other person is able to see. This is different from a network consensus failure, stolen assets, or transactions suddenly becoming invalid. For ordinary holders, I’d rather first check the wallet version in use, the type of proof, and who it is being shared with. I wouldn’t panic and transfer funds because of an unmerged PR. As for valuation, a fix under review shows that developers are addressing edge cases, but it does not create measurable new demand. Recent popular discussions on the forum have still focused mainly on the Binance security incident. XMR’s absence from the official first batch of withdrawal assets is consistent with Binance having delisted XMR earlier; it should not be used to infer anything about this PR or a new regulatory ban.

As of writing, Kraken’s XMR/USD is around $604.88, with a 24-hour range of $588.50 to $609.88. It is stronger than the opening price of $599.03, but has not broken above the range high. This reaction is not enough to prove that the market is pricing in the PR. I see $609.88 as short-term resistance and $588.50 as support. If the price breaks above resistance and then quickly falls back, that would signal insufficient appetite to chase. If it breaks below support and cannot recover it, my cautious outlook would strengthen. I’ll only revise how I describe technical progress after seeing the code merged, an official release note, and verification results on the wallet side.

If I were trading this myself, I wouldn’t chase the rally now; I’d only prepare a small spot position in the direction of the trend. I’d consider a long using 2% of total trading capital only if the price holds above $610, retests without breaking below it, and broader market volatility has not expanded significantly. I’d first target $620 and sell half there, with the remainder targeting $630. I’d set the initial stop-loss at $598 and close the entire position if it is triggered. If the stop-loss has not been hit but the price falls back below $610 and continues weakening, I’d exit early. If $588.50 is lost first, I’d cancel the plan and stay out of the market. No high leverage, and I won’t describe untriggered conditions as realized gains.

#XMR
The above is solely my personal market observation and does not constitute investment advice.

XMR wallet proof boundaries may tighten｜Code still awaiting merge｜Stay disciplined around $598

My stance is to watch cautiously and not chase a rally based on a single code review update. On October 31, the official Monero code repository saw PR #11655, which proposes having wallets refuse to generate a specific type of recipient proof, InProof, for transactions they have sent themselves. The submitter explained that when the payer sends an output to an address they control, certain proof materials could also expose information related to change; the proposed code would have the wallet reject this path if it recognizes that it has spent an input or holds the transaction key. The repository page shows that one reviewer has approved the proposal, but its status is still Open. The latest official release visible on the official blog is still version 0.18.5.4 from October 16. Review approval, code merge, a new release, and users actually upgrading are four different stages; this should not be described as a privacy upgrade already completed across the network.

This detail affects the privacy boundaries when users choose to share transaction proofs. It does not mean that Monero transfers have suddenly lost their privacy, nor is it evidence of “on-chain funds being stolen.” In the same proposal, the developers listed proof types that are not yet covered, including transaction keys, send proofs, and reserve proofs. So I’m more interested in whether subsequent reviews complete the boundary definitions and testing than in presenting a single patch as a universal fix. For the price of XMR, wallet reliability can support the long-term user experience, but it is difficult to infer short-term buying pressure directly from an unmerged PR. Current trending topics on Binance Square are focused on the recovery of exchange security; XMR is neither an asset named as affected in those announcements nor is there any basis to link it to the hacker attribution. Market risk appetite may be affected by security incidents, but that is part of the broader trading environment, not volatility caused by this PR.

At the time of writing, the latest trade on Kraken’s XMR/USD pair was about $597.91, with a daily open around $587.54 and an intraday range of approximately $585.65 to $601.05. It is fair to say the price is above the daily open but has not broken the intraday high; it is not fair to say the PR drove the rise. My levels to watch are resistance at $601–$602, a pullback zone around $592, and an invalidation level at $585. If the price breaks above $602 and then immediately falls back below $597, the short-term breakout thesis is invalidated. If a subsequent official announcement gives a more serious interpretation of the proof risks, I should reduce risk first rather than stick to the original plan.

If I were trading this myself, I would currently stay out. For now, I would only consider a small spot long and would not use futures. I would only take a trial position with 2% of my total funds if XMR/USD holds firmly above $602, then pulls back and holds $600, while broader market risk does not continue to spread. My first target would be $610, where I’d sell half; the second target would be $618, with the remainder trimmed in stages if momentum weakens. I’d place a stop below $594 and close immediately if it is triggered. If the price breaks below $585 first, I’d cancel all buy orders. Even if the conditions are met, I’d reassess if the project team withdraws the proposal or there is new adverse news about exchange security. A plan that hasn’t been triggered is not a position, let alone a profit.

Sources: Monero official GitHub PR #11655, Monero official blog, Kraken XMR/USD market data. #XMR
The above is only my personal market observation and does not constitute investment advice.