terence

@terencechain

53 Following

167015 Followers

terence pfp

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

0 reply

17 recasts

88 reactions

terence pfp

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

1 reply

24 recasts

116 reactions

terence pfp

Any farcaster fantasy football league this year?

10 replies

12 recasts

105 reactions

terence pfp

8 replies

35 recasts

86 reactions

terence pfp

0 reply

11 recasts

60 reactions

terence pfp

EIP-7732(ePBS) breakout call #6 notes: https://hackmd.io/@ttsao/epbs-breakout6

2 replies

4 recasts

125 reactions

terence pfp

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

0 reply

1 recast

78 reactions

terence pfp

12 replies

14 recasts

141 reactions

terence pfp

New post on builder bidding behaviors in ePBS, inspired by "Strategic Bidding Wars in On-chain Auctions". In the post we explore market changes from MEV-Boost to bid p2p and builder RPC, and discover a new single bluff strategy on p2p. Special thanks to @soispoke for the review! 🔗 https://ethresear.ch/t/builder-bidding-behaviors-in-epbs/20129 🔗 https://arxiv.org/abs/2312.14510

1 reply

25 recasts

85 reactions

terence pfp

17 replies

109 recasts

280 reactions

terence pfp

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

1 reply

6 recasts

156 reactions

terence pfp

Here are the slides during ethcc on pipelining ethereum consensus & execution. While many discuss pbs for trust, censorship, and latency, few highlight its benefits for better slot utilization, more execution time & DA time. https://docs.google.com/presentation/d/1Il19qu0b7gr7GBUCNkr-aRh8lqxmBX5OSqfv5mVtTAA/edit?usp=sharing

3 replies

18 recasts

122 reactions

terence pfp

7 replies

60 recasts

210 reactions

terence pfp

epbs breakout #4 call notes, check the highlighted section for a quick TLDR: https://hackmd.io/@ttsao/epbs-breakout4

0 reply

5 recasts

167 reactions

terence pfp

10 replies

62 recasts

173 reactions

terence pfp

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

2 replies

3 recasts

140 reactions

terence pfp

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.

1 reply

21 recasts

116 reactions

terence pfp

7 replies

83 recasts

192 reactions

terence pfp

Timeboost is a new transaction ordering design/policy we have been studying for a while. It resembles an execution auction where the winner gains fast lane access instead of re-ordering right. I'm curious to hear anyone's feedback. https://forum.arbitrum.foundation/t/constitutional-aip-proposal-to-adopt-timeboost-a-new-transaction-ordering-policy/25167

2 replies

8 recasts

127 reactions

terence pfp

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

0 reply

0 recast

188 reactions