Agenda
- blob-devnet-0
- bal devnets
- epbs-devnet-1
- debug RPC update
gm
gm gm :)
gm
Gm
gm
gm
gm
gm
gm
gm
omg is this gonna be a Pari episode?!?!?!
Reacted to "omg is this gonna be..." with ❤️
Reacted to "omg is this gonna be..." with ❤️
Reacted to "omg is this gonna be..." with ❤️
Reacted to "omg is this gonna be..." with ❤️
Reacted to "omg is this gonna be a Pari episode?!?!?!" with ❤️
Replying to "omg is this gonna be..." he never gets this excited when I host the call
Reacted to "omg is this gonna be..." with ❤️
Heeft gereageerd op "omg is this gonna ..." met ❤️
crap I can't hear anything, anyuone speaking?
Reacted to "he never gets this e..." with 😅
Reacted to "he never gets this excited when I host the call" with ❤️
Reacted to "he never gets this e..." with ❤️
Reacted to "he never gets this e..." with 😬
Reacted to "he never gets this e..." with ❤️
Reacted to "he never gets this e..." with ❤️
Replying to "crap I can't hear an..." Yes they are speaking
Reacted to "omg is this gonna be..." with ❤️
Replying to "https://notes.ethere..." I'd like to add 2780 to devnet4 since it effects every tx would be good to get sight of it soon
any takes on devnet-4 date?
What’s the number of the EIP?
2780 is still waiting for the benchmarks anyway?
2780
Reacted to "2780" with 👍🏼
https://notes.ethereum.org/@ethpandaops/bal-devnet-4 changed and mentions other two gas changes instead of 2780. Honestly solid and stable 8037 may be enough for 4. 3 repricing eips is too much on top of it. Or include 1 something simple
if we were done (end in sight) with 8037 i'd be behind adding 2780
Would prefer stability over adding another EIP. (for interop’s sake)
Heeft gereageerd op "Would prefer stabi..." met ➕
Reacted to "Would prefer stabili..." with ➕
Reacted to "Would prefer stabi..." with ➕
Reacted to "Would prefer stability over adding another EIP. (for interop’s sake)" with ➕
Reacted to "https://notes.ethere..." with 👍
Reacted to "Would prefer stabili..." with ➕
Replying to "EIP-7976 and EIP-798..." The changes are simple in the tests too afaik
EIP-7976 (specs and tests): https://github.com/ethereum/execution-specs/pull/2115 EIP-7981 (specs and tests): https://github.com/ethereum/execution-specs/pull/2144
Reacted to "EIP-7976 (specs): ..." with 🔥
Reacted to "EIP-7976 (specs): ht..." with 🔥
Reacted to "EIP-7976 (specs): ..." with 🔥
Heeft gereageerd op "EIP-7976 (specs): ..." met 🔥
Reacted to "EIP-7976 (specs): ..." with 🔥
How do I get into the breakout room again :D
Reacted to "EIP-7976 (specs and ..." with 🔥
Reacted to "EIP-7976 (specs and ..." with 🔥
Reacted to "EIP-7976 (specs and tests): https://github.com/ethereum/execution-specs/pull/2115 EIP-7981 (specs and tests): https://github.com/ethereum/execution-specs/pull/2144" with 🔥
Replying to "How do I get into th..." i think there'll be a popup
what does that mean?
Reacted to "i think there'll be ..." with 👍
Reacted to "Screenshot2026_04_..." with 😂
Reacted to "Screenshot2026_04_13_161748.jpg" with 😂
Reacted to "Barnabas has sent yo..." with 😂
Reacted to "Screenshot2026_04_..." with 😂
Reacted to "Barnabas has sent yo..." with 😂
Reacted to "Barnabas has sent yo..." with 😂
Heeft gereageerd op "Screenshot2026_04_..." met 😂
Reacted to "Screenshot2026_04_13_161748.jpg" with 😂
Reacted to "Barnabas has sent yo..." with 😂
Reacted to "Screenshot2026_04_13_161748.jpg" with 😂
Reacted to "Screenshot2026_04_13_161748.jpg" with 😂
Reacted to "Barnabas has sent yo..." with 😂
Reacted to "i think there'll be ..." with 👍
Reacted to "Screenshot2026_04_13_161748.jpg" with 😂
at least one finalized block?
Wouldn’t this depend on snap vs full sync?
yes, i think we would backwards sync right over the unfinalized section.
For at least the WSP yeah
who is responsible for reorging in case we have a massive parallel fork?
There is a fallback to snap sync in case the state of the parent is missing though - not sure this can be triggered for the scenarion in discussion
why is it significant?
"I want to have that in writing" ;)
I’ll have a quick writeup soon
Reacted to "I’ll have a quick wr..." with ❤️
Heeft gereageerd op "I’ll have a quick..." met ❤️
Reacted to "I’ll have a quick wr..." with ❤️
i remain unsure but writeup can be consulted by rest of team, pretty quickly
Reacted to "I’ll have a quick wr..." with ❤️
@Potuz how is it different from initial sync? In initial sync you also give us Payload/FCU and we get it from the network
I get it now what the issue is 🙂
marc
When we do init sync we do send you the payloads
LH doesn't
But they verify the hash
Thanks 🙂
Am I the only one that doesn’t see a breakout?
I dont
i don’t either
Can you add me Pari to the ePBS one?
I can’t see it
CL breakout pls
EL
EL
Menu bar: More > Breakout Rooms
Agenda
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.