terence pfp

terence

@terencechain

53 Following
167027 Followers


terence pfp
terence
@terencechain
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
28 recasts
154 reactions

terence pfp
terence
@terencechain
https://github.com/terencechain/consensus-specs/pull/2
0 reply
0 recast
1 reaction

terence pfp
terence
@terencechain
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
134 reactions

terence pfp
terence
@terencechain
Any farcaster fantasy football league this year?
11 replies
19 recasts
105 reactions

terence pfp
terence
@terencechain
Gm
8 replies
35 recasts
136 reactions

terence pfp
terence
@terencechain
FOCIL vs BRAID
0 reply
22 recasts
98 reactions

terence pfp
terence
@terencechain
Without more than a high-level Ethereum research post or a 35-minute video, it's hard to judge how simple or difficult BRAID is. I'm typically in the "devil is in the details" camp. One thing BRAID simplifies over something like FOCIL is that it doesn't require introducing a third type of actor (inclusion list constructor). Without this additional actor and duty, your slot anatomy flows just the same as today, avoiding conflicts over how to split the 12-second slot time, which I discussed more here: https://ethresear.ch/t/inclusion-list-timing-constraints/20198 BRAID's complexity will revolve around fork choice, consensus changes, and dealing with DOS and free DA. It takes a more from-scratch approach, which is often cleaner but will require more research and engineering cycles to fully understand its full implications.
0 reply
0 recast
3 reactions

terence pfp
terence
@terencechain
Hi Davide, ePBS (EIP-7732: block auction) opens the door for APS. It's the first attempt to organize market structure into the protocol. If this is successful, we can look into extending it to slot auction, future slot auction, ET/EA. We have to start somewhere : ) I'm interested to hear feedback on whether ePBS is not forward compatible with APS from you and the RIG team!
1 reply
0 recast
0 reaction

terence pfp
terence
@terencechain
EIP-7732(ePBS) breakout call #6 notes: https://hackmd.io/@ttsao/epbs-breakout6
2 replies
4 recasts
125 reactions

terence pfp
terence
@terencechain
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
103 reactions

terence pfp
terence
@terencechain
Gm
12 replies
36 recasts
267 reactions

terence pfp
terence
@terencechain
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
145 reactions

terence pfp
terence
@terencechain
Gm
17 replies
109 recasts
438 reactions

terence pfp
terence
@terencechain
Definitely, proposer can submit empty list if it wants
1 reply
0 recast
0 reaction

terence pfp
terence
@terencechain
That's the property of this inclusion list mechanism (forward-based): for a block to be accepted, it must also include one inclusion list to be enforced for the next slot proposer.
1 reply
0 recast
0 reaction

terence pfp
terence
@terencechain
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
228 reactions

terence pfp
terence
@terencechain
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
terence
@terencechain
Gm
7 replies
80 recasts
372 reactions

terence pfp
terence
@terencechain
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
terence
@terencechain
Gm
11 replies
62 recasts
253 reactions