12370

11 views
3 Discussing
交易的芋圆
·
--
ZEC Node Mempool Fix Reported|Not an On-Chain Double Spend|Wait for Confirmation Around $1,260 My stance is cautious and watchful. On November 8, the Zebra node project maintained by the Zcash Foundation saw a proposed fix that is still in draft status: when a parent transaction is removed from the mempool due to capacity policies, its dependent child transactions are removed as well, but the caller submitting a child transaction may still receive an “accepted” response. The issue and code changes are publicly available for review. The proposal is numbered #12370 and is currently Open and Draft; it has not been merged, much less released as a live fix. The scope of this issue needs to be clear. It concerns status feedback for unconfirmed transactions in a node’s mempool, which could lead merchants or wallets to believe a transaction is being held by the node, only to later discover that the node has actually removed it. This does not mean that a transaction confirmed on the blockchain has been reversed, nor does it indicate ZEC theft, a mainnet double spend, or a failure of the consensus rules. The proposed code is intended to record each transaction that is removed and return the same rejection result to submitters whose transactions are removed directly or removed as dependencies; the mempool eviction policy itself is unchanged. Tests have been added to check the response and retry behavior after parent and child transactions are removed together, but adding tests to a draft does not mean the fix has been released in an official version. Why does this matter to the market? The value of payments also depends on whether wallets and merchants can distinguish between “broadcast” and “confirmed.” If a service provider treats a node’s submission response as final receipt of payment, a status mismatch could affect user experience and risk controls. The extent of any losses would still depend on how service providers handle unconfirmed transactions; a single proposal does not establish that the entire network is malfunctioning. The upcoming NU7 upgrade and this node feedback fix are on different levels and should not be conflated as one catalyst. The market reaction has offered no optimistic confirmation. ZEC/USDT on Binance is around $1,260.70, down about 4.00% over the rolling 24-hour period from $1,313.29, with a high of $1,330.08 and a low of $1,236.64. Farside’s ZCSH flow data shows an outflow of about $11 million on November 5 and an inflow of about $1.8 million on November 6; these should not be combined into a claim of “sustained institutional buying.” Nor can the price decline be directly attributed to today’s draft proposal. ZEC appears under Most Searched on Binance Square, but has no Rapid Riser tag, and there is no related topic under Trending. I view the area around $1,236 as a short-term risk line and the area around $1,330 as resistance overhead. A break below $1,236 followed by a failed reclaim would indicate that the market is absorbing the risk less well than expected. Only a sustained move back above $1,330 accompanied by volume would make it reasonable to discuss a move beyond expectations for a recovery. More importantly, the view would need to be reassessed if officials confirm the scope of the issue, merge the code, and release a version, or if evidence emerges of serious real-world losses. In that case, the assessment must be revisited rather than carried over from today. If I were trading this myself, I would stay out for now: the stance is watchful, with 0% of my portfolio allocated. I would consider a small long position using no more than 0.4% of total capital only if ZEC spot price regains and holds above $1,330, then retests without breaking below it, while official updates do not indicate an expansion of the risk. I would not use leverage. The first target would be around $1,360, where I would take half off; I would close the rest around $1,390 or if price stalls on heavy volume. I would place a stop-loss if price falls back below $1,290 after entry. If price first breaks below $1,236, the original long plan is invalidated and I would remain flat rather than average down against the trend. I would also close any trial position if the merge is delayed, the scope of node risk expands, or a platform experiences withdrawal issues. If the plan is not triggered, there is no trade—and no profit to speak of. #ZEC The above is solely my personal market observation and does not constitute investment advice.
ZEC Node Mempool Fix Reported|Not an On-Chain Double Spend|Wait for Confirmation Around $1,260

My stance is cautious and watchful. On November 8, the Zebra node project maintained by the Zcash Foundation saw a proposed fix that is still in draft status: when a parent transaction is removed from the mempool due to capacity policies, its dependent child transactions are removed as well, but the caller submitting a child transaction may still receive an “accepted” response. The issue and code changes are publicly available for review. The proposal is numbered #12370 and is currently Open and Draft; it has not been merged, much less released as a live fix.

The scope of this issue needs to be clear. It concerns status feedback for unconfirmed transactions in a node’s mempool, which could lead merchants or wallets to believe a transaction is being held by the node, only to later discover that the node has actually removed it. This does not mean that a transaction confirmed on the blockchain has been reversed, nor does it indicate ZEC theft, a mainnet double spend, or a failure of the consensus rules. The proposed code is intended to record each transaction that is removed and return the same rejection result to submitters whose transactions are removed directly or removed as dependencies; the mempool eviction policy itself is unchanged. Tests have been added to check the response and retry behavior after parent and child transactions are removed together, but adding tests to a draft does not mean the fix has been released in an official version.

Why does this matter to the market? The value of payments also depends on whether wallets and merchants can distinguish between “broadcast” and “confirmed.” If a service provider treats a node’s submission response as final receipt of payment, a status mismatch could affect user experience and risk controls. The extent of any losses would still depend on how service providers handle unconfirmed transactions; a single proposal does not establish that the entire network is malfunctioning. The upcoming NU7 upgrade and this node feedback fix are on different levels and should not be conflated as one catalyst.

The market reaction has offered no optimistic confirmation. ZEC/USDT on Binance is around $1,260.70, down about 4.00% over the rolling 24-hour period from $1,313.29, with a high of $1,330.08 and a low of $1,236.64. Farside’s ZCSH flow data shows an outflow of about $11 million on November 5 and an inflow of about $1.8 million on November 6; these should not be combined into a claim of “sustained institutional buying.” Nor can the price decline be directly attributed to today’s draft proposal. ZEC appears under Most Searched on Binance Square, but has no Rapid Riser tag, and there is no related topic under Trending.

I view the area around $1,236 as a short-term risk line and the area around $1,330 as resistance overhead. A break below $1,236 followed by a failed reclaim would indicate that the market is absorbing the risk less well than expected. Only a sustained move back above $1,330 accompanied by volume would make it reasonable to discuss a move beyond expectations for a recovery. More importantly, the view would need to be reassessed if officials confirm the scope of the issue, merge the code, and release a version, or if evidence emerges of serious real-world losses. In that case, the assessment must be revisited rather than carried over from today.

If I were trading this myself, I would stay out for now: the stance is watchful, with 0% of my portfolio allocated. I would consider a small long position using no more than 0.4% of total capital only if ZEC spot price regains and holds above $1,330, then retests without breaking below it, while official updates do not indicate an expansion of the risk. I would not use leverage. The first target would be around $1,360, where I would take half off; I would close the rest around $1,390 or if price stalls on heavy volume. I would place a stop-loss if price falls back below $1,290 after entry. If price first breaks below $1,236, the original long plan is invalidated and I would remain flat rather than average down against the trend. I would also close any trial position if the merge is delayed, the scope of node risk expands, or a platform experiences withdrawal issues. If the plan is not triggered, there is no trade—and no profit to speak of.

#ZEC
The above is solely my personal market observation and does not constitute investment advice.
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number