XMR: Watch 633 support first | Pending-payment warning is still in development | Don’t treat a wallet proposal as bullish
My stance on XMR is cautious and watchful, especially when it comes to treating “seeing an incoming payment in the transaction pool” as a final receipt of funds. PR #11679, submitted to Monero’s core repository on November 4, proposes exposing to higher-level interfaces flags for double spends already detected in unconfirmed incoming transactions via the wallet API. The corresponding official GUI PR #4767 proposes warning merchants of potential double spends when receiving payments, and explicitly depends on the core PR and a submodule update. Both pages currently show “Open”; the GUI’s “next release” label is only a target release tag, not confirmation that it has been released. The official website’s blog still lists October 16’s 0.18.5.4 as the latest official GUI and core release. Pending code must not be described as complete protection already available in current wallets, nor should these two proposals be taken as evidence that large-scale double spending is currently occurring on mainnet.
This affects the discipline around payment confirmations. An unconfirmed transaction is still in the mempool and may be replaced, dropped, or conflict with another transaction. If a merchant hands over goods that cannot be recovered based only on a balance notification, the risk is very different from waiting for on-chain confirmation. The proposals add a more timely risk signal; they do not guarantee that every conflict can be detected in advance, nor do they turn zero-confirmation payments into final settlement automatically. My independent assessment is that payment confirmation requirements should be set according to the amount, counterparty, and reversibility of delivery, and that a payment should be accepted only when client and node information agree. For high-value, irreversible deliveries, it is better to wait. Wallet users should also verify signed versions from the official website and avoid treating a PR branch as an official installer.
News and price should be considered separately. Today’s trending topics on Binance Square are focused on the phased resumption of withdrawals at an exchange, reserve replenishment, and macro employment; XMR is not among the most-searched topics over the past six hours. I won’t ride unrelated hashtags for attention. On October 28, the Federal Reserve kept its target rate at 3.75% to 4%, leaving a funding-cost constraint on risk assets, including XMR, but this alone cannot explain current volatility. A Kraken snapshot shows XMR at around $635.22, with an opening price of $641.39 today, an intraday range of $633.12–$644.26, and a rolling 24-hour range of $624.75–$647.02. The current price is below today’s open, and the market has not clearly repriced upward in response to the wallet proposal; nor can the pullback be directly blamed on this PR.
My key levels are 633 and 625 as support, and 644 and 647 as resistance. If 633 breaks and a retest fails to reclaim it, my short-term stabilization thesis is invalidated, and I’ll focus on the possibility of renewed pressure near 625. If price holds above 647 consistently and spot trading volume improves, I’ll consider entering in the direction of the move with a small position. If project maintainers change the proposal’s direction or the released version differs from the current draft, I’ll review the details again rather than rely on my previous assumptions.
If I were trading this myself: I would stay out for now and only consider a leveraged-free spot long. The planned position size for any single trade would be no more than 1% of total capital. The entry trigger is to first reclaim 644, hold 640 on a pullback, and then break above 647; if any condition is missing, I’ll remain in cash. The first target is 655, where I’d take half off; the second target is 665, where I’d close the remaining position in stages. The initial stop-loss would be below 632. If price falls back below 633 after entry, I’d exit early rather than wait for the stop to trigger. If a new issue with payment risk is officially confirmed by the project, or liquidity rapidly deteriorates, I’d cancel pending orders and close the short-term position. This conditional plan does not mean that I have entered a trade or made a profit.
#XMR
The above is only my personal market observation and does not constitute investment advice.
My stance on XMR is cautious and watchful, especially when it comes to treating “seeing an incoming payment in the transaction pool” as a final receipt of funds. PR #11679, submitted to Monero’s core repository on November 4, proposes exposing to higher-level interfaces flags for double spends already detected in unconfirmed incoming transactions via the wallet API. The corresponding official GUI PR #4767 proposes warning merchants of potential double spends when receiving payments, and explicitly depends on the core PR and a submodule update. Both pages currently show “Open”; the GUI’s “next release” label is only a target release tag, not confirmation that it has been released. The official website’s blog still lists October 16’s 0.18.5.4 as the latest official GUI and core release. Pending code must not be described as complete protection already available in current wallets, nor should these two proposals be taken as evidence that large-scale double spending is currently occurring on mainnet.
This affects the discipline around payment confirmations. An unconfirmed transaction is still in the mempool and may be replaced, dropped, or conflict with another transaction. If a merchant hands over goods that cannot be recovered based only on a balance notification, the risk is very different from waiting for on-chain confirmation. The proposals add a more timely risk signal; they do not guarantee that every conflict can be detected in advance, nor do they turn zero-confirmation payments into final settlement automatically. My independent assessment is that payment confirmation requirements should be set according to the amount, counterparty, and reversibility of delivery, and that a payment should be accepted only when client and node information agree. For high-value, irreversible deliveries, it is better to wait. Wallet users should also verify signed versions from the official website and avoid treating a PR branch as an official installer.
News and price should be considered separately. Today’s trending topics on Binance Square are focused on the phased resumption of withdrawals at an exchange, reserve replenishment, and macro employment; XMR is not among the most-searched topics over the past six hours. I won’t ride unrelated hashtags for attention. On October 28, the Federal Reserve kept its target rate at 3.75% to 4%, leaving a funding-cost constraint on risk assets, including XMR, but this alone cannot explain current volatility. A Kraken snapshot shows XMR at around $635.22, with an opening price of $641.39 today, an intraday range of $633.12–$644.26, and a rolling 24-hour range of $624.75–$647.02. The current price is below today’s open, and the market has not clearly repriced upward in response to the wallet proposal; nor can the pullback be directly blamed on this PR.
My key levels are 633 and 625 as support, and 644 and 647 as resistance. If 633 breaks and a retest fails to reclaim it, my short-term stabilization thesis is invalidated, and I’ll focus on the possibility of renewed pressure near 625. If price holds above 647 consistently and spot trading volume improves, I’ll consider entering in the direction of the move with a small position. If project maintainers change the proposal’s direction or the released version differs from the current draft, I’ll review the details again rather than rely on my previous assumptions.
If I were trading this myself: I would stay out for now and only consider a leveraged-free spot long. The planned position size for any single trade would be no more than 1% of total capital. The entry trigger is to first reclaim 644, hold 640 on a pullback, and then break above 647; if any condition is missing, I’ll remain in cash. The first target is 655, where I’d take half off; the second target is 665, where I’d close the remaining position in stages. The initial stop-loss would be below 632. If price falls back below 633 after entry, I’d exit early rather than wait for the stop to trigger. If a new issue with payment risk is officially confirmed by the project, or liquidity rapidly deteriorates, I’d cancel pending orders and close the short-term position. This conditional plan does not mean that I have entered a trade or made a profit.
#XMR
The above is only my personal market observation and does not constitute investment advice.
