Your Daily Briefing on Ethereum News.

Joined November 2021
Ethereum Daily ~ October 18, 2025 Presented by @inflynce 💎 Huobi Founder Launching ETH DAT 💼 Dankrad Leaves for Tempo 🔥 BETH Builder Grants 💎 Earn ETH by reading today's issue in the mini app below!
83
6
113
3,641
Ethereum should be much faster. A faster Ethereum is better for both Ethereum and ETH. Many discussions in our offsite revolved around what I’d call fast Ethereum. We’ve already mentioned fast Ethereum in some of our updates, and I wanted to share a few notes on motivations, principles and concrete work. --- Ethereum is the hardest credible settlement layer in the world, with hundreds of billions of dollars of assets attached to it. Its speed matters to onboard the global economy: payments, swaps, credit, all at the speed of the Internet. Fast Ethereum is about making our network move at the pace of users, agents and assets, between L1 and Ethereum’s growth engines, its L2s. Fast Ethereum is about latency, about friction, about capital cost and about delightful experiences. Every second spent waiting for confirmation, or every minute capital sits idle between domains, or every minute that an asset issuer waits for settlement is friction imposed on the people and businesses using the network. We think Ethereum can remove much of that friction without compromising the properties that make it valuable in the first place. This unlocks value that all users receive from Ethereum and its applications, in particular financial applications that are powered by natively onchain assets. Bottom line: greater user value increases network value through network effects, increasing the value of the Ethereum platform and ETH the asset. --- This informs some of the principles behind Fast Ethereum. → Security is non-negotiable. Safely operating onchain is the base of the pyramid of user needs. Clear signing was for instance number 1 user priority for a long time. Latency reductions cannot come at the cost of increased user risk. → Fast Ethereum 🤝 lean Ethereum. Lower in the stack, the Ethereum protocol’s value to the world is its hardness. lean Ethereum is a broad effort to upgrade Ethereum’s protocol for a new age driven by formal verification and cryptographic innovation. Fast Ethereum works to complement lean Ethereum with a strong focus on protocol design and performance engineering for a faster network. → User value is at the centre of fast Ethereum. This is not about showing better headline numbers than other chains and platforms. As long as the network remains at the security level that all have come to expect from Ethereum, speed improves everything on our network, on our own terms: fewer clicks to get what you want, less time spent waiting for an action to terminate, less idle capital blocked by settlement, better prices, lower costs, less intermediation and more open markets. --- So how do we do this? Ethlabs is already active on multiple fronts, some shorter term, some longer term, some iterative, some transformative. No single upgrade will fix everything. But fixes compound with each other, each new fix unlocking more and more value over time. We’re in it for the long haul, as are core developers and builders working on these issues. The main deliveries we’re currently active on: fast blocks, fast finality, fast confirmation rule and fast interoperability. → Fast blocks is Mainnet’s block time, set today to 12 seconds. Faster blocks improve UX, onchain markets and liquidity, censorship resistance and finality itself. Block time is hard-coded to 12 seconds in many places, and removing this dependency is the first step. I proposed kicking off slot time decreases in Hegotá, with a one-time refactor to remove the hard-coded 12 seconds, and a first decrease from 12 to 10 seconds. → Fast finality is faster settlement of Ethereum, backed by the strongest assurances of any network. Faster finality reduces the time and the cost for capital to flow, between Mainnet, L2s and the broader economy. A first major improvement to finality is developed by @fradamt, EF Protocol and Consensys TX/RX, towards inclusion in I* (the fork following Hegotá), bringing time-to-finality down from a quarter of an hour to a couple minutes. → The Fast Confirmation Rule (FCR) is faster settlement in the order of tens of seconds we can deliver today, for many use cases that don’t require the economic security of full finality, speeding up deposits from L1 to other domains. FCR is provably secure under formally explicit conditions in ways that other confirmation rules (such as waiting for some number of blocks) are not. These less secure rules are currently in use by some centralised exchanges, bridges and L2s, and they also happen to be usually much slower than what FCR achieves. FCR is close to production in all major Ethereum clients, and our team @_julianma @decentrek and @ox_shaman is actively working on its go-to-market. A major bridge has recently committed to offering FCR to its customers, as @decentrek noted in his last update! → Fast interoperability is about the free flow of all assets on our network, offering asset issuers the foundations of a robust stack powered by Ethereum. Each of the previous items enhances interop speed in its own right. Beyond these compounding gains, a concerted move to real-time zk proving is a different tier of unlock: bridge flows from L2s to L1 remain slow, either due to the long challenge period of optimistic rollups, usually set to 7 days, or due to infrequent settlement of zk-rollups to L1, given the opportunity of amortising costs in batches. With zk becoming a commodity, we must ensure our ecosystem is ready to plug in to this new basic utility in order to reduce latency and improve security at scale. We also remain active on broader interoperability UX questions, having worked on fast liquidity from intent-based bridges and execution standards such as ERC-8211. --- To wrap up, we’re currently interested in two engagements from the community: 1. Hegotá priorities are currently debated for the next few weeks. We’ve already given our view as Ethlabs, ranking faster blocks as our S-tier choice: ethlabs.org/writings/hegota-… Continuing to express public support for faster blocks, as users, builders or core developers is a critical signal to ensure block time is reduced asap. Hegotá is possibly the last window to get started for a few years—let’s not miss it. 2. As go-to-market for the fast confirmation rule continues, we’re reaching out to L2s, bridges, RPCs and centralised exchanges for integration. If your product relies on some form of confirmation from Ethereum L1, we think a conversation would be valuable. Please reach out to @_julianma 🙂 Let’s grow Ethereum and ETH with a faster Ethereum.
29
54
11
295
46,176
Today on Ethereum News: The first $VITALIK coin launched on @pumpfun expands to Ethereum, forwards all fees to @VitalikButerin and is then censored and banned from the Pump platform. Could Pump deliberately be targeting Ethereum memecoins, or is this simply a misunderstanding?
5
3
9
1,485
Biggest BNB Chain LP and Token locker just exit scammed for 6 million dollars Current drained 2M usd + Money is being sent to binance One of the most tragic events being unfolded right now and no one is even aware 🙏
2
7
753
Ca they are exploiting 0xEb3a9C56d963b971d320f889bE2fb8B59853e449
2
3
268
Money is going to these addresses 0xb71c1C2A0cD7A88f1317f9A996e4d121E7db5E92 0x4c5ee9703653C8e7725C65593bff372655e0453C
1
160
I personally believe in privacy combined with decentralization however i think ethereum foundation should also invest heavily in truly private hardware development having privacy focused software is great however a chip on your device sending out information cant be stopped
I want to get a bit more public about the work we at the Kohaku Initiative inside the EF are doing I notice there's hype but there's also confusion. Best way to clarify things is to speak candidly and openly about what I'm working on day-to-day 🧵time (bc i dont pay twitter $)
4
578
X is mass suspending crypto accounts If you are not suspended you are super lucky! ID verified accounts seem to be unaffected. If you are not ID verified and you value your account i recommend you ID verify on X now. If personal information remain private it would be good @X
1
3
524
Ethereum Daily retweeted
ERC-8211 allows users and agents to express multi-step composable actions as a simple off-chain script with built-in safety.
48
200
19
717
141,865
Kohaku initiative is one of the most underlooked initiatives of Ethereum a must read 👇
At EthCC @VitalikButerin and @ncsgy did a presentation about our Kohaku initiative and both of them highlighted usage of AI agents / LLMs. I am getting convinced that in the case of the "ethereum access layer" (aka wallets) we can harness AI to leap ethereum UX forward 🧵
2
1
9
1,389
Ethereum Daily retweeted
We do not intend to move slowly.🫡
56
102
32
1,032
91,775
Ethereum Daily retweeted
EF, last year: Hey, we want to listen to you users to make Ethereum better. EF, now: Jk, we looked at the real world. We don't like building for it after all, we'll go back to building cypherpunk stuff only. This is the EF going back to its old ways, undoing the changes from last year. I have feared this would happen because Vitalik clearly wasn't in with his heart. But whatever they say about the "ecosystem" being able to take care of this, the fundamental problems remain: - there are very few voices in ACD caring about real world Ethereum usage - there is nobody doing Ethereum BD (everyone else who is doing this also has their own separate interests)
Today, the Foundation’s Board released the EF Mandate. This document, which was first intended for EF members, reaffirms the promise of Ethereum, and the role of EF within this ecosystem.
121
41
38
575
209,647
Ethereum Daily retweeted
0/ Privacy in the Ethereum ecosystem is undergoing an evolution. A Renaissance, even, to sound a bit fancy. What exactly is behind these changes and how might neo-Cypherpunk be involved? A guest thread by @post_polar_ and @nicksvyaznoy.
112
156
34
884
183,560
Ethereum Daily retweeted
How will vitalik.eth@base resolve once apps support interoperable addresses? The ENS name resolves the account, while the chain suffix resolves the execution environment through the on.eth chain registry. Both combine into a single interoperable address.
15
33
133
9,956
Ethereum Daily retweeted
If you need more details on the features/EIPs for strawmap, check out eth2030.com and github.com/jiayaoqijia/eth20…. Apart from the impl, more docs and refs can be found there for better understanding of @ethereum roadmap. cc @VitalikButerin @tkstanczak @hwwonx @drakefjustin @joshrudolf @DavideCrapis @barnabemonnot @GiulioRebuffo @ralexstokes @trent_vanepps @adietrichs @austingriffith
Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.
2
8
2
36
7,290
Ethereum Daily retweeted
Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8… ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-sta… firefly.social/post/farcaste…
790
1,075
320
5,667
946,668