Monero Core Development Proposal Fully Funded with 79 XMR｜v0.19 Still Has Pending Tasks｜I Won’t Chase a Bounce Around 568
My stance: Funding in place can improve development continuity, but it shouldn’t be written as if a protocol version has already been released. This morning, after scanning Binance Square’s trending pages, Binance’s official news, and macro regulatory updates, I returned to first-hand records from the Monero project. The community crowdfunding system shows that developer selsta’s three-month full-time development proposal has already raised 79/79 XMR. The proposal date is September 1st, with coverage planned for September through November. The work includes preparing small changes for v0.19.0.0, CLI and GUI, code review, building the release, and drafting documentation. The page shows only two backers and no milestone completion dates for September, October, or November. “Fully funded” refers to the funding status—it is neither confirmation that work for a given month has been accepted, nor a sign that the v0.19 mainnet has launched. I won’t use “upgrade completed” to create a false catalyst.
The second verification point is Monero’s official GitHub milestones. The release-v0.19 milestone shows 13 items: 11 closed and 2 still open, with no promised release date. This number can help gauge progress, but milestones are not a complete test report, and closing issues doesn’t mean every user is already safely upgraded. In the previous cycle, I looked at a 85 XMR proposal for a node replacement by Cuprate that still had a funding gap. This time, I’m looking at a different contributor—responsible for version consolidation and release—who has already been funded. They are not the same pot of money. For XMR, core development isn’t just a marketing slogan: if no one maintains wallets, nodes, and release engineering, the security and usability of privacy features will be affected. But if it’s only that crowdfunding is fully funded, with no new stable release and no real usage data, you also can’t infer an immediate buy order.
The order book doesn’t provide evidence that this old proposal strengthened the market. I checked KuCoin’s XMRUSDT perpetuals: the current price is around $568.4, with a 24-hour range of about $562.1 to $591.6. The completed 15-minute candles have stepped down from around 576, even dipping to 564.0, then rebounding from roughly 565.2 back to 568.4. In the short term, it looks like a repair after a drop, not confirmation of an upward trend. 570.5 to 571.5 is the first resistance zone; 574 to 576 is a higher supply area. If it breaks below 564 and stays there, the rebound scenario should be invalidated. The contract funding rate is slightly positive, suggesting long positions carry holding costs—and reminding me not to mistake a temporary surge for confirmed spot inflows. These quotes are only observation snapshots; things will change after the release.
If I were trading myself: I’m currently keeping an empty position. I would only consider conditional spot longs, using at most 0.6% of total capital. I’d wait for a full 15-minute close above 571.5, then a pullback to 570.5–571.5 that holds, and only participate in batches after the next candle also closes above 571.5. The first target is 574 to 576; at that point I’d reduce/halve. The remaining position would depend on conditions around 580, and I’d raise the stop-loss to breakeven. The initial stop-loss is set below 566. If a 15-minute close occurs below 566, and the price first breaks below 564, or if v0.19 release triggers substantial security disputes, I would close everything or cancel the plan. If it doesn’t trigger, I won’t trade—no leverage gambling on a version with no confirmed release date.
Source: Monero CCS selsta development proposal and monero-project official GitHub milestones; market data is a live snapshot of KuCoin XMRUSDTM.
#XMR
The above is only my personal market observation and does not constitute investment advice.
My stance: Funding in place can improve development continuity, but it shouldn’t be written as if a protocol version has already been released. This morning, after scanning Binance Square’s trending pages, Binance’s official news, and macro regulatory updates, I returned to first-hand records from the Monero project. The community crowdfunding system shows that developer selsta’s three-month full-time development proposal has already raised 79/79 XMR. The proposal date is September 1st, with coverage planned for September through November. The work includes preparing small changes for v0.19.0.0, CLI and GUI, code review, building the release, and drafting documentation. The page shows only two backers and no milestone completion dates for September, October, or November. “Fully funded” refers to the funding status—it is neither confirmation that work for a given month has been accepted, nor a sign that the v0.19 mainnet has launched. I won’t use “upgrade completed” to create a false catalyst.
The second verification point is Monero’s official GitHub milestones. The release-v0.19 milestone shows 13 items: 11 closed and 2 still open, with no promised release date. This number can help gauge progress, but milestones are not a complete test report, and closing issues doesn’t mean every user is already safely upgraded. In the previous cycle, I looked at a 85 XMR proposal for a node replacement by Cuprate that still had a funding gap. This time, I’m looking at a different contributor—responsible for version consolidation and release—who has already been funded. They are not the same pot of money. For XMR, core development isn’t just a marketing slogan: if no one maintains wallets, nodes, and release engineering, the security and usability of privacy features will be affected. But if it’s only that crowdfunding is fully funded, with no new stable release and no real usage data, you also can’t infer an immediate buy order.
The order book doesn’t provide evidence that this old proposal strengthened the market. I checked KuCoin’s XMRUSDT perpetuals: the current price is around $568.4, with a 24-hour range of about $562.1 to $591.6. The completed 15-minute candles have stepped down from around 576, even dipping to 564.0, then rebounding from roughly 565.2 back to 568.4. In the short term, it looks like a repair after a drop, not confirmation of an upward trend. 570.5 to 571.5 is the first resistance zone; 574 to 576 is a higher supply area. If it breaks below 564 and stays there, the rebound scenario should be invalidated. The contract funding rate is slightly positive, suggesting long positions carry holding costs—and reminding me not to mistake a temporary surge for confirmed spot inflows. These quotes are only observation snapshots; things will change after the release.
If I were trading myself: I’m currently keeping an empty position. I would only consider conditional spot longs, using at most 0.6% of total capital. I’d wait for a full 15-minute close above 571.5, then a pullback to 570.5–571.5 that holds, and only participate in batches after the next candle also closes above 571.5. The first target is 574 to 576; at that point I’d reduce/halve. The remaining position would depend on conditions around 580, and I’d raise the stop-loss to breakeven. The initial stop-loss is set below 566. If a 15-minute close occurs below 566, and the price first breaks below 564, or if v0.19 release triggers substantial security disputes, I would close everything or cancel the plan. If it doesn’t trigger, I won’t trade—no leverage gambling on a version with no confirmed release date.
Source: Monero CCS selsta development proposal and monero-project official GitHub milestones; market data is a live snapshot of KuCoin XMRUSDTM.
#XMR
The above is only my personal market observation and does not constitute investment advice.
