@wmougayar @HealthcareNFT @_julianma @joshrudolf The mechanism that guarantees censorship-resistance remains FOCIL. The recursive mempool is simply a mechanism to ensure that whatever lands onchain is maximally compressed. So FOCIL guarantees your ticket, this EIP just makes sure the train is packed efficiently (simplifying)

We reviewed all 60+ EIPs proposed for Hegotá and updated our view on what Ethereum should prioritize. Our rankings follow four themes: 1. Stronger censorship resistance: Ethereum can only become a settlement layer for everyone if it stays neutral toward everyone. We strongly support FOCIL. 2. Faster Ethereum: Shorter slots mean faster confirmations, fresher onchain prices, and faster finality. We strongly recommend Quick Slots to make a first reduction in Hegotá and further reductions easier in subsequent forks. 3. Native account abstraction: Ethereum is long-due for native AA. Frame Transactions bring passkey wallets, sponsored transactions, gas paid in tokens, batching, and better support for privacy and post-quantum security. Adoption will take work across wallets, L2s, and the rest of the stack, and we intend to keep helping with that. 4. Performance engineering: continued L1 scaling & a faster Ethereum. Performance should remain a first-class concern in both client work and protocol design. The gains can go toward more capacity, shorter slots, lower node requirements, or all three. Thanks to everyone who put forward proposals and helped us work through them. We’ll keep updating our view as client and testing teams assess the work involved. PS: find the full view + changelog here: PPS: finally an iPhone that fits all 60+ Hegota EIPs

🍵 New post: Mempool Account Transaction Capacity from Historical Activity (MATCHA) 🍵 tldr: Frame transactions allow apps to define their own validation and gas payment logic. But admitting many pending transactions from one sender creates a DoS risk: a malicious app could invalidate them all with one cheap state change, forcing nodes to repeat the validation work. MATCHA bounds this risk by making each additional admission spend capacity earned through finalized onchain activity. Its goal is to let many users share one sender without having to whitelist applications, paymasters or proof systems.

today EF Protocol published two posts. we hope you check them out! for me, they mark the end of a transition that started back in april. when @kevaundray, @0xfredrik, and i stepped into the cluster coordinator roles, the job within the job was cluster-wide alignment: shaping a strategy born from our imperative (concentrate Protocol on what only Protocol can and will do), grounded in CROPS, and aimed at what Ethereum needs right now to endure for 1,000 years. 1️⃣ the first post makes that strategy public: a quantum-resistant ethereum L1 by december 2029, the multi-fork plan to get there, and what each of our five research arcs needs from the upcoming forks. 2️⃣ the second post is our first unified hardfork opinion: grades from every team in the cluster, argued down to one tier list covering every EIP proposed for hegotá, with the reasoning behind every grade. read the priorities first. the tier list is those priorities applied. lastly, Protocol is hosting a Reddit AMA on r/ethereum, sept 16 at 2pm UTC. hope to see you there. question form in the next post. 👇

@DCinvestor currently writing a piece on how we use AI at @ethlabs_org, it’s really been a game changer to set up a new org with a shared context layer from day one. also @fradamt doing a ton of formal verification work accelerating fast Ethereum work 👀

Interesting to see Bitcoin and Ethereum PQ discussions converging on very similar questions. Block-wide PQ signature aggregation brings us to the same design space: circuits vs VMs, recursion, proof size, aggregators, soundness...

Precompiles continue to be a pain point for zkVMs: each one is a special case that needs its own hand-built proving logic, and they're among the slowest and most expensive parts of a block to prove. EIP-8200 aims at replacing precompiles with ordinary EVM bytecode. Same behavior, but a zkVM can prove it like any other contract. Plus it simplifies the protocol by removing a set of special cases every EL client has to implement and maintain separately. Precompiles today run natively inside EL clients as fast compiled code ('cheap gas'), while their replacements would run as interpreted EVM bytecode (slower, using more gas). Closing that gap is akin to gas-golfing: squeeze the bytecode until it's as cheap as possible. turns this into an open, verified challenge. Anyone with good prompts and sufficient token budget can compete —> AI accelerating L1 R&D (make sure to check out the other autoresearch challenges as well) EIP-8200 is PFI'd for Hegota and facilitates EIP-8025 (execution proofs on L1). This is the L1-zkEVM route to scaling; when validators verify proofs instead of re-executing every TX, so the gas limit can grow significantly: —> More premium blockspace, more onchain activity, more economic bandwidth on L1 itself

The SEC just proposed modernizing transfer agent rules, the framework governing custody and transfer of securities ownership, for the first time since the 1970s-80s. The proposal explicitly names blockchain as an acceptable way to handle these functions. This closes one of the last major regulatory gaps blocking institutions from moving securities settlement onto distributed ledger infrastructure. Banks and asset managers now have a clearer compliance path to adopt Ethereum-based tokenization platforms at scale. Weekly policy news for Ethereum and digital assets >

@sweetman_eth @ethlabs_org Glamsterdam (hard fork coming by end of this year) will raise the gas limit to minimum 200M afaik, ie, a 3x improvement, which should lower gas costs dramatically. Hegotá, which will feature native account abstraction, may also increase the limit further.

One overlooked aspect of EIP-8141 is privacy. Frame Transactions let privacy pools sponsor withdrawals directly from the withdrawal amount, removing the relayer needed today. The next step is STARK aggregation, which can push the cost of privacy pool interactions close to zero. Frame Transactions are also the foundation for native privacy and utxos, mempool aggregation and more. Quite bullish Ethereum.

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: 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.