Creator Pulse: Ethereum removes the Hoodi upgrade date as Starknet opens L1 research

Hoodi's postponed upgrade changes the testing calendar

The Ethereum Foundation's 22 October postponement notice removes the Glamsterdam activation previously scheduled for Hoodi on 26 October at 17:42:48 UTC. It also removes the associated increase to a 200 million gas limit. Developers are investigating interactions between EIP-8037 and mainnet smart contracts, and no replacement activation date has been set. The notice concerns a testnet and requires no action from Ethereum mainnet users.

Why now: Any article, calendar or operator checklist still presenting the original activation as upcoming needs correction. The fresh development is the withdrawal of a specific schedule. It changes what teams can test next week and what node operators should expect their configurations to do. An earlier announcement remains part of the timeline, but its activation instructions have been superseded.

An angle worth explaining: A network upgrade begins before an activation block. Client software, operator configurations and applications all prepare around the announced rules. Postponement therefore involves coordination as well as a revised date. Removing the future activation configuration prevents the old plan from continuing merely because some software still expects it.

For creators, the useful narrative follows the people doing that work. A node operator needs release instructions that explicitly reflect the postponement. An application team needs to revise a testing plan. A mainnet user needs an accurate account of the scope, without being told that a testnet delay is a live mainnet incident. Those audiences face different consequences from the same notice.

The strongest counterargument to treating the delay as evidence of failure is that investigation before activation is part of the purpose of a testnet process. The stronger critical question is whether the interactions can be explained, resolved and tested across clients. That question can be answered through subsequent technical disclosures, while speculation about a replacement date adds little.

What remains uncertain: The notice provides no revised activation time or completed account of the investigation. A claim that the issue has already been fixed, or that a particular mainnet date has moved, would go beyond the announcement.

Starknet's vote starts a research process

Starknet's post-poll governance update, published on 22 October, reports 93.52% of voting power in favor of researching an independent, post-quantum L1. The Foundation says a joint research group will examine the requirements and trade-offs, publish findings and seek further approval if detailed proposals follow. The poll does not authorize a transition.

Why now: The result changes the status of the idea from a discussion into an organized research effort. That creates a useful reporting sequence: the question being investigated, the assumptions behind it, the eventual design and the later decision. Collapsing that sequence into a claim that Starknet is leaving Ethereum would erase the steps participants have yet to complete.

An angle worth explaining: A system can have promising cryptographic components while retaining dependencies on another system. The Foundation's stated motivation includes the security implications of Ethereum-linked infrastructure. The analytical question is whether independence would improve the complete security model after accounting for the new responsibilities it creates. A creator can explore that decision without endorsing the Foundation's assessment of its own technology.

The most productive comparison is between concrete architectures: where data would be made available, how assets would cross systems, which parties would validate the network and how users would migrate. Independence could reduce some inherited dependencies while requiring replacement mechanisms. The research must show how those mechanisms would operate together. A favorable poll cannot supply that technical answer.

What remains uncertain: The percentage measures voting power in this poll. It does not establish the proportion of all users who support an eventual move, and the reviewed update does not provide a participation denominator adequate for that broader claim. The research outcome and any final architecture remain open.

Uniswap makes external liquidity part of its routing system

Uniswap Labs says Aggregator Hooks are live in its web app and API on Ethereum, Base and Robinhood Chain. Seven sources are connected at launch. The company describes hooks that wrap external liquidity so routers can see it as v4 pools, with a route settling in one transaction. It also says routed swaps pay protocol fees that contribute to UNI burn.

Why now: This is a deployed product announcement with a mechanism creators can examine. It provides a more concrete subject than a broad claim that decentralized exchanges are consolidating. The feature changes how an interface can assemble a trade, while the actual share of trading that uses the new routes still needs to be measured.

An angle worth explaining: There are several roles in a swap: the interface where the user starts, the router choosing a path, and the venue supplying liquidity. They can belong to different operators. Connecting outside liquidity can make the interface more useful without moving that liquidity into a new pool. That distinction helps explain why routing reach and liquidity ownership are different competitive advantages.

The fee question makes the story more consequential. If externally supplied liquidity can support trades that pay Uniswap protocol fees, the economic boundary of the routing system can expand beyond its native pools. That is the mechanism Uniswap describes. The investment conclusion still depends on how much traffic takes those routes and the resulting fees; deployment alone does not quantify either.

A useful creator format would trace one completed swap: where the liquidity sat, which path the router chose, and where the fees went. That makes the competitive roles visible without deriving a token-price forecast from the launch.

What remains uncertain: Uniswap's estimate that the connected sources cover more than 90% of DEX activity on the named chains is an issuer estimate. It is neither the share already routed through the hooks nor evidence of realized fee revenue.