eridian.eth (@EridianAlpha) header
eridian.eth (@EridianAlpha) profile picture

Ethereum Settler 💻

Ethereum
Joined April 2021
Weekly Roundup ePBS, distilled 🔗 ethresear.ch/t/25800 10 comment(s) this week Demand Model with Elasticities for Ethereum State, Data, and Execution and Glamsterdam Fee Market Analysis 🔗 ethresear.ch/t/25644 2 comment(s) this week Proposed PQ upgrade for ecrecover 🔗 ethresear.ch/t/25844 1 comment(s) this week Temporal Liquidity: heterogeneous demand and Ethereum's single execution lane 🔗 ethresear.ch/t/25840 1 comment(s) this week Proof boundaries in a minimal homomorphic tally for token weighted voting 🔗 ethresear.ch/t/25831 1 comment(s) this week An Evaluation of Authenticated UTXO Discovery with EIP-8304 and UTXO Proof Tables 🔗 ethresear.ch/t/25828 1 comment(s) this week AMM Yield Maximization: Convergence of the Liquidity Provider and Arbitrageur Roles 🔗 ethresear.ch/t/25826 1 comment(s) this week When Multiple Pools Behave Like One: Impact-Constrained Capacity Concentration in Uniswap v3 🔗 ethresear.ch/t/25823 1 comment(s) this week Proprietary AMMs and Ethereum 🔗 ethresear.ch/t/25543 1 comment(s) this week Manipulation-Resistant Prediction Market Derivatives with Language Models 🔗 ethresear.ch/t/20660 1 comment(s) this week Timing the Head in Ethereum PoS 🔗 ethresear.ch/t/25766 1 comment(s) this week Lenientic: Preparing legal disputes arising from smart contracts for AI resolution 🔗 ethresear.ch/t/11261 1 comment(s) this week
3
7
642
1/ We’re excited to announce the close of @ethereuminsti's initial ecosystem funding round and supporter coalition, with broad participation and support from individuals and entities focused on driving institutional adoption of @ethereum. Our ecosystem funding round is anchored by @BitMNR, @Sharplink, Ethereum co‑founders @ethereumJoseph , and @MihaiAlisie, alongside a larger group of individuals and crypto‑native institutions.
167
340
163
1,768
1,269,552
eridian.eth retweeted
Replying to @ethereum
@ethereum turns 11 today. 11 years of uninterrupted operation. 100% uptime. Along the way, it has become the leading settlement layer for stablecoins, the leading network for tokenized assets, the largest developer ecosystem in crypto, and the foundation of DeFi. The institutions building the future of finance are choosing Ethereum.
7
19
1
158
17,005
Replying to @VitalikButerin
@VitalikButerin just set the stage in Hong Kong! 🇭🇰✨ Key insights from his fireside chat with #DuncanChiu: ✅ Layer 2: L2 is a "free market" critical for scaling & innovation. ✅ Scaling Roots: L1 remains essential for data & computation growth. ✅ Future Tech: Quantum resistance & AI integration are the big plays for the next 3-5 years. #Ethereum #VitalikButerin #HongKongWeb3 #Layer1 #Layer2 #AI #ETHHKHub
4
17
538
🔥The moment we’ve all been waiting for 🚀 We are incredibly excited to announce that @VitalikButerin, Co-Founder of @ethereum, will be joining us in person at the Grand Opening of the ETH HK Hub! This marks his first-ever visit to our dedicated community space in Hong Kong. This visit continues his long-term support for APAC builders. It’s the start of a new decade for the Ethereum community in Asia ⚡️ Be part of history. Witness the future 🎉 Request your invite now: 🔗 luma.com/uf5v6joa 📍 Hong Kong Ethereum Community Hub 📅 April 21 | 13:30 - 18:00
5
6
3
28
3,900
A great event yesterday by @ETHCapitalHQ supporting the Ethereum community in Seoul 🇰🇷 with talks from @drakefjustin and @no89thkey on the future of Ethereum scaling
2
151
eridian.eth retweeted
The best case scenario is Realtime Ethereum with realtime swaps, lending, and trading. @lepsoe lays it all out on his episode of the @11AMdotclub livestream.
73
15
105
16,104
eridian.eth retweeted
PropAMMs now account for 40–50% of 0x Swap API volume on @base. They enable tighter spreads, but without accountability, execution quality suffers. We monitor it closely so your users can trust every quote.
6
7
54
6,913
eridian.eth retweeted
Last night, our Product Safety Lead joined Builder Nights Cannes to speak on “Who sets and what are the Agent Guardrails?” 🇫🇷🔥 An insightful panel discussing safety and governance in Ethereum. Excited for what’s next!
82
6
2
101
13,733
eridian.eth retweeted
Lido Day @ EthCC9 Cannes 🇫🇷 A day for builders, stakers, node operators, and institutional teams to talk all things Ethereum staking. Thank you all for coming 🩵
6
16
2
82
4,891
eridian.eth retweeted
At the @blueyard Utopia vs Oblivion Summit in LA and there are a few key takeaways: 1. Maria Corina Machado @MariaCorinaYA is WOW, super inspiring and with a fascinating story using tech at so many different levels (not to mention fighting for democracy..duh!)
1
2
9
1,795
New post on EthResear.ch! Outcome Preconfs: Verifying Block Commitments Without the Block By: - jvranek 🔗 ethresear.ch/t/24466 Highlights: - Core problem: proposers must verify preconfirmation (preconf) commitments are satisfied before signing a block, but inspecting the full block body leaks the builder’s block and breaks fair exchange. - Relays can verify constraints today (optimistic/pessimistic), but ePBS removes relays from the critical path, so a relay-based trusted verifier is no longer a viable default. - Merkle-proof-based verification is trustless but has two major drawbacks: (1) proof generation adds latency after block construction, and (2) it is not expressive enough for many stateful/transaction-level outcome claims (e.g., proving a specific transaction caused a specific state change) without re-execution or ZK proofs. - EIP-7928 Block Access Lists (BALs) offer a low-latency, non-leaking verification substrate: BALs are produced as a byproduct of execution, committed in the header, capture every state write with a global ordering index, and omit transaction inputs/signatures—enabling verification of outcomes without revealing the full block contents. - By shifting from transaction commitments to outcome preconfs, any preconf type (inclusion, ordering/top-of-block, execution outcomes, exclusion/absence, threshold checks) can be expressed as a first-order-logic (FOL) formula over the BAL, letting one fixed verifier implementation handle new preconf types as new formulas rather than new infrastructure (with BALs also serving as dispute evidence for off-chain/on-chain adjudication). ELI5: Sometimes a block proposer wants to promise users something about the next block (like “your payment will happen” or “this contract gets updated first”). But before the proposer signs the block, they must check the promise was kept—without seeing the whole block, because seeing it would let them steal it from the builder. Older approaches either rely on trusted middlemen (relays) or require slow/limited proofs. This post suggests using a new kind of “receipt” called a Block Access List (BAL): a structured list of what the block changed in Ethereum’s state (balances, storage slots, nonces, etc.), in what order, but without revealing the actual transactions. Then the proposer can check promises by asking simple true/false questions about that list, using one common “question language,” for many different promise types.
4
6
28
1,921
eridian.eth retweeted
Proposal: Introducing Identified DVT Clusters (IDVTC) to Lido CSM This proposal brings a tailored bonded DVT solution to the Lido Community Staking Module, accelerating DVT adoption and furthering the resilience of CSM. ↓
15
17
4
82
13,135
eridian.eth retweeted
The first Open Gas rebate is live. Gas fees on Ethereum have always been a hidden tax on users. Today, our partner protocols start subsidizing them for you.
169
25
5
152
241,883
eridian.eth retweeted
Finally, the block building pipeline. In Glamsterdam, Ethereum is getting ePBS, which lets proposers outsource to a free permissionless market of block builders. This ensures that block builder centralization does not creep into staking centralization, but it leaves the question: what do we do about block builder centralization? And what are the _other_ problems in the block building pipeline that need to be addressed, and how? This has both in-protocol and extra-protocol components. ## FOCIL FOCIL is the first step into in-protocol multi-participant block building. FOCIL lets 16 randomly-selected attesters each choose a few transactions, which *must* be included somewhere in the block (the block gets rejected otherwise). This means that even if 100% of block building is taken over by one hostile actor, they cannot prevent transactions from being included, because the FOCILers will push them in. ## "Big FOCIL" This is more speculative, but has been discussed as a possible next step. The idea is to make the FOCILs bigger, so they can include all of the transactions in the block. We avoid duplication by having the i'th FOCIL'er by default only include (i) txs whose sender address's first hex char is i, and (ii) txs that were around but not included in the previous slot. So at the cost of one slot delay, only censored txs risk duplication. Taking this to its logical conclusion, the builder's role could become reduced to ONLY including "MEV-relevant" transactions (eg. DEX arbitrage), and computing the state transition. ## Encrypted mempools Encrypted mempools are one solution being explored to solve "toxic MEV": attacks such as sandwiching and frontrunning, which are exploitative against users. If a transaction is encrypted until it's included, no one gets the opportunity to "wrap" it in a hostile way. The technical challenge is: how to guarantee validity in a mempool-friendly and inclusion-friendly way that is efficient, and what technique to use to guarantee that the transaction will actually get decrypted once the block is made (and not before). ## The transaction ingress layer One thing often ignored in discussions of MEV, privacy, and other issues is the network layer: what happens in between a user sending out a transaction, and that transaction making it into a block? There are many risks if a hostile actor sees a tx "in the clear" inflight: * If it's a defi trade or otherwise MEV-relevant, they can sandwich it * In many applications, they can prepend some other action which invalidates it, not stealing money, but "griefing" you, causing you to waste time and gas fees * If you are sending a sensitive tx through a privacy protocol, even if it's all private onchain, if you send it through an RPC, the RPC can see what you did, if you send it through the public mempool, any analytics agency that runs many nodes will see what you did There has recently been increasing work on network-layer anonymization for transactions: exploring using Tor for routing transactions, ideas around building a custom ethereum-focused mixnet, non-mixnet designs that are more latency-minimized (but bandwidth-heavier, which is ok for transactions as they are tiny) like Flashnet, etc. This is an open design space, I expect the kohaku initiative @ncsgy will be interested in integrating pluggable support for such protocols, like it is for onchain privacy protocols. There is also room for doing (benign, pro-user) things to transactions before including them onchain; this is very relevant for defi. Basically, we want ideal order-matching, as a passive feature of the network layer without dependence on servers. Of course enabling good uses of this without enabling sandwiching involves cryptography or other security, some important challenges there. ## Long-term distributed block building There is a dream, that we can make Ethereum truly like BitTorrent: able to process far more transactions than any single server needs to ever coalesce locally. The challenge with this vision is that Ethereum has (and indeed a core value proposition is) synchronous shared state, so any tx could in principle depend on any other tx. This centralizes block building. "Big FOCIL" handles this partially, and it could be done extra-protocol too, but you still need one central actor to put everything in order and execute it. We could come up with designs that address this. One idea is to do the same thing that we want to do for state: acknowledge that >95% of Ethereum's activity doesn't really _need_ full globalness, though the 5% that does is often high-value, and create new categories of txs that are less global, and so friendly to fully distributed building, and make them much cheaper, while leaving the current tx types in place but (relatively) more expensive. This is also an open and exciting long-term future design space. firefly.social/post/lens/814…
284
351
55
1,419
279,259
eridian.eth retweeted
Now, scaling. There are two buckets here: short-term and long-term. Short term scaling I've written about elsewhere. Basically: * Block level access lists (coming in Glamsterdam) allow blocks to be verified in parallel. * ePBS (coming in Glamsterdam) has many features, of which one is that it becomes safe to use a large fraction of each slot (instead of just a few hundred milliseconds) to verify a block * Gas repricings ensure that gas costs of operations are aligned with the actual time it takes to execute them (plus other costs they impose). We're also taking early forays into multidimensional gas, which ensures that different resources are capped differently. Both allow us to take larger fractions of a slot to verify blocks, without fear of exceptional cases. There is a multi-stage roadmap for multidimensional gas. First, in Glamsterdam, we separate out "state creation" costs from "execution and calldata" costs. Today, an SSTORE that changes a slot from nonzero -> nonzero costs 5000 gas, an SSTORE that changes zero -> nonzero costs 20000. One of the Glamsterdam repricings greatly increases that extra amount (eg. to 60000); our goal doing this + gas limit increases is to scale execution capacity much more than we scale state size capacity, for reasons I've written before ( ethresear.ch/t/hyper-scaling… ). So in Glamsterdam, that SSTORE will charge 5000 "regular" gas and (eg.) 55000 "state creation gas". State creation gas will NOT count toward the ~16 million tx gas cap, so creating large contracts (larger than today) will be possible. One challenge is: how does this work in the EVM? The EVM opcodes (GAS, CALL...) all assume one dimension. Here is our approach. We maintain two invariants: * If you make a call with X gas, that call will have X gas that's usable for "regular" OR "state creation" OR other future dimensions * If you call the GAS opcode, it tells you you have Y gas, then you make a call with X gas, you still have at least Y-X gas, usable for any function, _after_ the call to do any post-operations What we do is, we create N+1 "dimensions" of gas, where by default N=1 (state creation), and the extra dimension we call "reservoir". EVM execution by default consumes the "specialized" dimensions if it can, and otherwise it consumes from reservoir. So eg. if you have (100000 state creation gas, 100000 reservoir), then if you use SSTORE to create new state three times, your remaining gas goes (100000, 100000) -> (45000, 95000) -> (0, 80000) -> (0, 20000). GAS returns reservoir. CALL passes along the specified gas amount from the reservoir, plus _all_ non-reservoir gas. Later, we switch to multi-dimensional *pricing*, where different dimensions can have different floating gas prices. This gives us long-term economic sustainability and optimality (see vitalik.eth.limo/general/202… ). The reservoir mechanism solves the sub-call problem at the end of that article. Now, for long-term scaling, there are two parts: ZK-EVM, and blobs. For blobs, the plan is to continue to iterate on PeerDAS, and get it to an eventual end-state where it can ideally handle ~8 MB/sec of data. Enough for Ethereum's needs, not attempting to be some kind of global data layer. Today, blobs are for L2s. In the future, the plan is for Ethereum block data to directly go into blobs. This is necessary to enable someone to validate a hyperscaled Ethereum chain without personally downloading and re-executing it: ZK-SNARKs remove the need to re-execute, and PeerDAS on blobs lets you verify availability without personally downloading. For ZK-EVM, the goal is to step up our "comfort" relying on it in stages: * Clients that let you participate as an attester with ZK-EVMs will exist in 2026. They will not be safe enough to allow the network to run on them, but eg. 5% of the network relying on them will be ok. (If the ZK-EVM breaks, you *will not* be slashed, you'll just have a risk of building on an invalid block and losing revenue) * In 2027, we'll start recommending for a larger minority of the network to run on ZK-EVMs, and at the same time full focus will be on formally verifying, maximizing their security, etc. Even 20% of the network running ZK-EVMs will let us greatly increase the gaslimit, because it allows gas limits to greatly increase while having a cheap path for solo stakers, who are under 20% anyway. * When ready, we move to 3-of-5 mandatory proving. For a block to be valid, it would need to contain 3 of 5 types of proofs from different proof systems. By this point, we would expect that all nodes (except nodes that need to do indexing) will rely on ZK-EVM proofs. * Keep improving the ZK-EVM, and make it as robust, formally verified, etc as possible. This will also start to involve any VM change efforts (eg. RISC-V) firefly.social/post/lens/104…
329
306
67
1,902
281,050
A great week at @EthereumDenver listening to talks from @VitalikButerin, @dannyryan, @lepsoe, and many others! A smaller event this year, but high signal as always.
1
113
Tonight I'll be speaking about scaling Ethereum on the @MetaMask Builder Nights panel, discussing how @ETHGasOfficial is pushing the boundaries of what is possible on the L1 today and building a Realtime future
Replying to @MetaMask
💡 Scaling the Stack: Infra That Actually Ships with: @realJustinCPA (@summ_app) @EridianAlpha (@ETHGasOfficial) @P3b7_ (@Ledger) @FletchMcCraw (@DINBuild)
1
98