Ladislaus (ladislaus)

This is your chance to ask EF researchers and developers directly The EF Protocol teams are hosting a Reddit AMA on August 29 Submit your questions about scaling L1, scaling blobs, improving UX, and a lot more now😎 🔗⬇️

• 3 replies
• 4 recasts
• 8 reactions

Hey Farcaster ethr&d friends, I wanted to share a quick summary of our latest beam call This one focused on the peer-to-peer networking layer Read on 👇 & watch the recording attached

• 1 reply
• 2 recasts
• 5 reactions

https://hackmd.io/@austonst-aestus/BJsvEoia6 (Sophisticated) validators play timing games to optimize for value extraction. Relays like Aestus offer them as a service to any validator. How does this level the playing field among validators? What are risks and tradeoffs? see more below 👇

• 0 replies
• 0 recasts
• 0 reactions

This is your chance to ask EF researchers and developers directly The EF Protocol teams are hosting a Reddit AMA on August 29 Submit your questions about scaling L1, scaling blobs, improving UX, and a lot more now😎 🔗⬇️

• 3 replies
• 4 recasts
• 8 reactions

Hey Farcaster ethr&d friends, I wanted to share a quick summary of our latest beam call This one focused on the peer-to-peer networking layer Read on 👇 & watch the recording attached

• 1 reply
• 2 recasts
• 5 reactions

It's still imperfect & leaves altruistic validators with a binary option, but with the recent harmonization of the 'builder boost factor' across clients stakers may now express more granular payload preferences. Worth pointing out :) https://paragraph.xyz/@ethstaker/enhancing-censorship-resistance-options-for-stakers

• 0 replies
• 1 recast
• 1 reaction

We'll likely see even more centralised actors along the block building pipeline, e.g. sequencers, preconfirmers & gateways. That may be OK, as long as we have means to *not let them mess* with the chain. Inclusion Lists are such a mean. https://x.com/mikeneuder/status/1768717158362595525?s=20

• 0 replies
• 1 recast
• 1 reaction