Wrote a post on FOCIL resource considerations after reflecting on how clients might implement it. We outlined some concerns about potential bottlenecks, hoping to spark more discussions to move it toward the spec realization phase. Feedback welcome! https://ethresear.ch/t/focil-resource-design-considerations/20457
ePBS breakout #8 notes: https://hackmd.io/@ttsao/epbs-breakout-8
Moving to slot auctions seems imminent at this point, the question is when. If we want to have slot auctions for the very first client devnet, then the sooner the better
New post on inclusion list timing constraints: Different designs bring different timing limitations for inclusion list actors. We argue there's no perfect design due to trade-offs within an Ethereum slot. Feedback welcome.
https://ethresear.ch/t/inclusion-list-timing-constraints/20198
Here are my slides for ethcc on redefining trust between proposer and builder through ePBS. Today, to use a builder, a proposer MUST trust a relayer, which carries invisible costs across multiple domains: money, latency, fault, schedule, and healthy market dynamics. I argue that these costs become cheaper (or go away) with ePBS. Enjoy! https://docs.google.com/presentation/d/1Jw0EZvkZzzeKWi-yehwLWdIl4VEZ1Le9_ywDrFDS6Oc/edit?usp=sharing
EIP7732 is live! 🎉 The first EIP on ePBS and separating proposer and builder roles. This EIP focuses on block auctions, but future work could extend to slot or ticket auctions. Feel free to take a look and ask any questions.
https://eips.ethereum.org/EIPS/eip-7732
New post on fork choice attacks in EPBS: https://ethresear.ch/t/fork-choice-attacks-and-protections-in-epbs/19951. I covered existing write-ups on EPBS post-anti, ex-anti, and new builder reorg and withholding attacks, including the new boost values and why some attacks are more useful than others. Feedback welcome.
Curious to hear what's the downside of this strawman idea to make the current blob market more efficient:
- 90% of blocks are built by the builder
- Rollups submit blobs directly to the builder's blob mempool or something like Flashbots RPC
- Builder’s mempool allows white-listed addresses from rollups. Adopt a less strict version of mempool rules:
- Allow white-listed addresses to submit a vector of blob txs with varying blob counts (1-6)
- These vectors can have different tip amounts
- Implement a less restrictive tip replacement rule for these addresses
- Assuming a few rollups opt-in, the builder can mix and match blob txs from different rollups more efficiently than before, improving market clearing...
