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.
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.
