36073

Geth proposes limiting the number of transactions submitted in a single request | Node abuse resistance still under review | ETH near $2,228; staying on the sidelines for now

My view is to treat improvements to node security as long-term infrastructure progress, while maintaining discipline in the short term. Pull request #36073 for Ethereum execution client Geth was proposed on November 5. It would add a limit of 100 transactions per batch to the transaction-submission subprotocol used by browsers. The author explained that the previous limit only capped message size at 1 MB, but smaller legacy transactions could allow roughly 10,000 transactions to fit in one message. Before rejecting the entire batch, the transaction pool would still have to perform signature recovery and validation for each transaction. The author’s local tests on an M1 Pro showed that signature recovery alone could use about 0.4 seconds of CPU time. The proposal would reject requests containing more than 100 transactions as protocol violations before they reach the transaction pool, and add boundary tests. These figures come from the author’s tests on a specific machine; they do not mean the entire network has already been attacked or that all nodes would incur the same costs.

What matters to me is the “cost asymmetry”: if there is too large a gap between sending a small message and making nodes perform extensive validation, service quality can be undermined by abuse. Node connection stability can affect users’ experience when submitting transactions through wallets and, in extreme cases, transaction propagation as well. But this patch applies only to a specific Geth submission path; it does not mean Ethereum throughput has increased, gas fees have fallen, or consensus rules have changed. The repository page still shows the PR as Open, review by code owners is still pending, and the branch is marked as not deployed. One participant approving the change is no substitute for a formal merge and release. The chain of reasoning required to turn a code proposal directly into bullish news for ETH is too long.

The market is also reminding me to prioritize fund flows. Farside currently lists U.S. ETH fund net flows for November 5 as an outflow of $99.9 million, including $75.2 million out of ETHA and $22 million out of ETHB; these are verified figures from the previous reporting period, not a new round of outflows. At the time of writing, Kraken ETH/USD was around $2,228, with an opening price of $2,235.09 and a 24-hour low of $2,202.12 and high of $2,432.44. The price is near the bottom of the range, but there has been no independently identifiable rally prompted by the Geth proposal. Current trending topics on Binance Square focus on exchange withdrawals and a sharp drop in U.S. stocks. ETH is among the most-searched terms, but there is no popular topic directly related to this code proposal, so I won’t add unrelated tags. The U.S. employment report has not yet been released either, and macro volatility could still overshadow project-level developments.

If I were trading for myself, I would stay out for now and only prepare a conditional, unleveraged spot long, with a planned position size capped at 1% of total capital. I would need to see the price regain and hold above $2,250, then successfully retest that level, and confirm that fund flows are not deteriorating further. Only then would I enter in two tranches. My first target would be $2,290, where I would sell half; my second target would be $2,350, where I would close the rest. If the price falls below $2,202 after entry, I would immediately stop out and close the position. I would also exit early if the U.S. employment data triggered a sharp sell-off, the price fell back below $2,250, or the code review uncovered an issue. If the current conditions are not met, my position remains at 0%. If the price breaks below $2,202 and stays there, the original long setup is invalidated; I would wait for new information rather than averaging down.

Sources: Official Ethereum Geth GitHub PR #36073, Farside ETH fund flows table, Kraken ETH/USD market data, Binance Square trending page. #ETH
This is solely my personal market observation and does not constitute investment advice.

Geth proposes limiting bulk submissions from browsers｜ETH still around 2380｜I’m waiting for risk confirmation

My stance is cautious and watchful. The official repository for Ethereum execution client Geth opened a new PR #36073 today, proposing a 100-transaction limit per batch for the browser transaction submission subprotocol. The developer explains that this path is currently limited to about 1 MB by message size; if it contains only small, legacy transactions, a single message could still hold a large number of them, requiring nodes to recover signatures and validate transactions against the transaction pool one by one. The proposal aims to reject oversized batches before this computation begins, and includes tests showing that batches at the limit can enter the transaction pool while those exceeding it are rejected at the protocol layer. The page is currently marked Open; the PR has not been merged or released. This is a preventive tightening of a potential resource-consumption pathway—it should not be described as an attack on Ethereum mainnet, nor should we say that users are already subject to the new limit.

This change affects the workload nodes face when handling abnormal requests, not ETH issuance or transaction demand. If it ultimately passes review and testing and is included in a client release, some nodes may become more resistant to abuse. The author cites the fact that an ordinary wallet’s submissions are far below the proposed limit as a design rationale, but real-world deployment still needs to be validated. More importantly, a software security proposal should not be directly translated into a price catalyst for the day. Current trending topics on Binance Square still lean toward exchange recoveries and US macro developments. ETH is among the most searched terms, but there is no trending topic directly related to this Geth proposal, so I won’t use an unrelated hashtag.

The market has already shown signs of weak risk appetite. Kraken ETH/USD is around $2,385, below the daily open of $2,422, with an intraday low of about $2,383 and a high of $2,434; the rolling 24-hour high is around $2,447. The $2,405 support I was watching previously has been lost, and the price has not yet recovered it convincingly. This decline cannot be attributed to the PR that was just proposed. Institutional flows also need to be considered by date: Farside data shows net inflows of $53 million into US spot ETH funds on November 4, but net outflows of about $139.7 million and $85.3 million on November 2 and 3, respectively, with flows diverging across products on November 4. The November 5 row still shows dashes; the displayed total of 0.0 merely means the data is pending and should not be described as a complete absence of institutional flows that day. The Fed held rates at 3.75%–4% at its last meeting, and the official US October employment report is scheduled for release tomorrow. With the data window approaching, a one-day rebound in flows should not be treated as confirmation of a trend.

For the short term, I’m watching the intraday low near $2,380. To the upside, $2,405 is the first level to watch, followed by $2,422–$2,435. If $2,380 breaks and cannot be reclaimed, the weak outlook remains in place. If the price gets back above $2,405 but falls again before reaching $2,422, that would only be an attempted recovery. To overturn my current cautious view, ETH would need to hold steadily above $2,435 after the data is released, with subsequent flow disclosures showing no renewed weakening.

If I were trading myself, I wouldn’t open a new position right now; I would only consider a conditional spot long. I would enter a test position using no more than 1% of my total funds only if, after the employment data is released, ETH regains and holds above $2,435 and then retests it without breaking below. The first target would be $2,447, where I would take half off; I’d hold the rest for $2,470. If the price falls back below $2,405 after entry, I would stop out and close the position. If the conditions never trigger, I would remain in cash. No leverage throughout, and I would not use research progress as a reason to chase the price.

#ETH
The above is only my personal market observation and does not constitute investment advice.