11650

XMR coin control is still a draft | Official wallet feature not yet released | Stay cautious below 647

My stance is to wait for implementation, not chase the news. Pull request #4762 in Monero’s official GUI repository proposes adding a “Coins” tab to the advanced interface, letting users view and freeze or unfreeze individual outputs in their wallets. It was submitted on October 30 and is currently marked Draft. It depends on pull request #11650 in the core wallet repository, which would provide interfaces for freezing, unfreezing, and viewing output details; that request is also still Open and awaiting review. The latest stable GUI version listed on the project website remains 0.18.5.4, released on October 16. The accurate description is that this is a wallet feature under development—not that it is already available in an official release, and certainly not that it is a Monero protocol upgrade or that an on-chain incident has occurred.

Why is it worth discussing? Monero’s privacy does not mean wallet operations require no discipline. The choice of which spendable outputs to use in a payment affects how users manage fund sources and wallet records. “Freeze” here means the local wallet temporarily refrains from selecting a particular output; it does not freeze on-chain assets or mean that outsiders have the right to seize a balance. If officially released in the future, a visual coin-control feature could help people who need to separate incoming payment batches. But it comes with a learning curve: accidentally freezing outputs can make the available balance appear smaller, and users will need to understand the unfreezing and backup processes. The project is still reviewing the proposal, and there is no factual basis for claims of direct benefits to trading volume, privacy strength, or the coin’s price.

I view this development in the broader market context. A current trending topic on Binance Square concerns self-custody declarations in France, but an earlier vote in the French parliament on related amendments does not mean a final law has taken effect, and it did not name XMR. The wallet draft and regulatory rumors cannot be combined into the conclusion that “privacy coins are about to be banned.” On October 28, the Federal Reserve held its policy rate at 3.75%–4%, so risk assets still face changes in liquidity and macroeconomic expectations. A Kraken XMR/USD quote snapshot showed about $634.59, below that day’s open of $641.39. The day’s approximate low and high were $633.12 and $644.26, while the rolling 24-hour range was about $624.75–$647.02. The price shows no clear demand to chase the announcement. In the short term, watch $633.12 first, then $624.75 if that level breaks. To recover, the price would need to get back above $644.26 and $647.02. If it falls below $624.75 and fails to recover quickly, the view that the market is in a mild consolidation becomes invalid.

If I were trading this myself, I would stay out for now and consider only a small, unleveraged spot long. I would wait for the hourly chart to close above $647.02, hold that level on a retest, and confirm that commonly used trading channels and market depth are normal. Only then would I place a test trade using no more than 1% of my total capital. The first target would be $655, where I would sell half; the second would be $665, with a trailing stop to manage the remaining position. I would stop out if the price fell below $633.12 after entry. If it cannot reclaim and hold $647.02 within two days, or if the official team discloses new facts affecting wallet security, I would close the position immediately. If none of these conditions is met, I remain out of the market, with no trade or profit to review.

Sources: Monero GUI #4762, Monero core wallet #11650, the project website’s release history, and a Kraken quote snapshot. #XMR

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

XMR Wallet May Add Output Controls | GUI Proposal Still a Draft | Waiting for 603 Confirmation

My stance is to wait and see, and to distinguish a code proposal from a usable feature. On October 30, a proposal for the Monero official code repository, #11650, appeared to add wallet interface functions for freezing, unfreezing, and viewing details of encrypted outputs. A corresponding GUI wallet proposal, #4762, would add a “Coins” tab to the advanced page, letting users choose which outputs to exclude from future payments. The two proposals depend on each other: the GUI page is still marked Draft, and the underlying interface remains Open. They show that developers are working on output controls at the wallet level; they do not mean that all XMR wallets have been updated, much less that the Monero network has undergone a hard fork.

This kind of feature relates to privacy, but its mechanics need to be described accurately. A Monero balance usually consists of multiple outputs, and the wallet selects available outputs when making a payment. Temporarily freezing an output restricts the user’s own wallet from selecting it; it does not freeze the coins on-chain or mean that funds held by a third-party exchange are locked. For people who regularly receive funds from different sources, manually controlling outputs may help with bookkeeping. Misuse could also create unnecessary privacy linkages or make the spendable balance appear insufficient. Developers still need to address state persistence, rescanning, and interface notifications. The final experience can only be evaluated after the feature is merged, released, and tested. Current security incidents at popular exchanges are custodial-platform risks; this wallet proposal should not be presented as a fix for those incidents.

Price action does not show any independent impact from this proposal. At around 10 p.m. Beijing time tonight, XMR/USD on Kraken was around $594, with a 24-hour high and low of about $601 and $572, respectively, still within a short-term range. Broader risk sentiment and platform liquidity also affect the quote. My key resistance zone is $601–$603; below, I’m watching $585 first, then $572. If code review stalls, the GUI draft is withdrawn, or XMR falls below $585 and fails to recover quickly, the short-term bullish thesis weakens. Even if the proposal is merged in the future, that would only mean the feature has entered the codebase; it would not by itself imply user adoption or a price increase.

If I were trading it myself, I would stay out for now. The only direction I would consider is a small spot long, capped at 2% of total capital. The entry trigger would be two consecutive one-hour XMR candles holding above $603, with no fresh liquidity shock in the market; the feature proposal itself is not a trading trigger. If I entered, I would take half off at the first target of $615, then half of the remaining position at the second target of $628. I would close the rest if the price fell back below $603. The initial stop-loss would be around 2% below the entry price. If the price first breaks below $585, I would cancel this plan and remain out of the market. If a future official release does not include the feature, I would withdraw the medium-term view based on it rather than dressing up development discussions as a benefit that has already been delivered.

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