terence pfp

terence

@terencechain

53 Following
167258 Followers


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
3 recasts
53 reactions

terence pfp
terence
@terencechain
Gm
19 replies
44 recasts
184 reactions

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
4 replies
7 recasts
93 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
7 recasts
58 reactions

terence pfp
terence
@terencechain
Gm
11 replies
33 recasts
160 reactions

terence pfp
terence
@terencechain
epbs breakout #4 call notes, check the highlighted section for a quick TLDR: https://hackmd.io/@ttsao/epbs-breakout4
1 reply
9 recasts
67 reactions

terence pfp
terence
@terencechain
Gm
11 replies
21 recasts
116 reactions

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

terence pfp
terence
@terencechain
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.
2 replies
5 recasts
71 reactions

terence pfp
terence
@terencechain
Gm
11 replies
27 recasts
127 reactions

terence pfp
terence
@terencechain
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
3 replies
7 recasts
51 reactions

terence pfp
terence
@terencechain
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
1 recast
61 reactions

terence pfp
terence
@terencechain
Gm ā˜ļø
12 replies
40 recasts
176 reactions

terence pfp
terence
@terencechain
3.) I think we can solve the blob market with the above, but there may still be times that builders refuse to accept blob txs. Builders don't run default client software. One solution to fix this is to just tell posters to increase the tip until builders include it. Another solution is a protocol force inclusion list for blob transactions, which we haven't thought much about. Excited to see how this develops!
0 reply
6 recasts
46 reactions

terence pfp
terence
@terencechain
2.) The current blob market is inefficient at matchmaking; it doesn't clear well. Most posters submit their best strategy blob tx. Given the max blob per block is 6, posters may send a tx with 1 to 6 blobs. Postersā€™ best strategy may change; Alice sent 6 blobs at time t1, then Bob sent 1 blob with a higher tip at t2. The builder picks Bob's tx because of the higher tip. If Alice had known Bob's intent, Alice would have sent 5 blobs at t1 instead of 6. To fix this, we either need a more relaxed version of the mempool that accepts a "menu" of txs and allows mix-matching. A relaxed mempool leads to DoS risk, so it would make sense to be done on the builder side and maybe just accept whitelisted senders to begin with. Another solution is to have a secondary market to mix-match blob txs to maximize social wellfair.
3 replies
11 recasts
108 reactions

terence pfp
terence
@terencechain
Last smol post on unpacking the current blob market issue as far as what I can see. I can't claim I have a good solution to any of this, but I'm excited to see how it unfolds in the coming months. 1.) Blob tip is not an independent field. It's shared with execution tip. The total tip paid is execution tip multiplied by gas usage. Given two txs, one with higher execution usages than the other, the tip will be higher but that doesn't tell anything about how many blobs there are. Example: {blob_count: 6, tip: 2, gas_used: 5} beats out {blob_count: 1, tip: 9, gas_used: 1} even though it's paying a higher total tip in the end. It's not clear to me who simulates, I was told some builders already simulate, but the cleanest solution is to give the blob tip its own field.
2 replies
6 recasts
53 reactions

terence pfp
terence
@terencechain
ePBS breakout call #3 notes: https://hackmd.io/@ttsao/epbs-breakout3
0 reply
3 recasts
50 reactions

terence pfp
terence
@terencechain
Stylus is now live on Arbitrum Sepolia: https://arbitrumfoundation.medium.com/welcome-to-the-stylus-blitz-hackathon-0d8b27e0c057
2 replies
15 recasts
113 reactions

terence pfp
terence
@terencechain
Compiled an FAQ for the top ePBS questions: https://hackmd.io/@ttsao/epbs-faq0. More to come as we get new questions! Feel free to ask publicly or DM me for clarifications. Your feedback is welcome!
3 replies
10 recasts
101 reactions

terence pfp
terence
@terencechain
What are the best technical specs or detailed literature available on pre-confs? I know the basics, but really want to dive deeper into the technical parts.
2 replies
6 recasts
60 reactions