Agenda
Agenda
- Summary of interop event
- glamsterdam devnet updates
- spec glamsterdam next devnet
- debug RPC update
gm
gm gm
gm
gm 🙂
gm
gMonday
Gm
what an agenda today
gm gm
crap can't hear anything.
Me too
Is anyone talking? 🙂
not right now
Reacted to "Is anyone talking? 🙂" with 😃
but now
sssh
Reacted to "not right now" with 😂
my sound has been tested and it has passed the test
Reacted to "my sound has been tested and it has passed the test" with 👏
Reacted to "my sound has been te..." with 👏
Interop recap: https://blog.ethereum.org/2026/05/02/soldogn-interop-recap
https://gist.github.com/qu0b/f3f905cadee4464a1a941838a5a5fadb
Just managed to log in here, @Barnabas I don’t think we finalized anything invalid
Client’s aren’t serving the right payloads though it seems
Reacted to "my sound has been te..." with 👏
Replying to "Client’s aren’t serv..." On finalized slots or recent hot payloads?
Replying to "Client’s aren’t serv..." We’re unable to sync unfinalized
I can share Hegota testing later
Heeft gereageerd op "I can share Hegota..." met 💙
anyone can see a way to recover devnet 3?
Fixing sync seems like it would do the trick?
Replying to "Client’s aren’t serv..." still debugging on lodestar side trying to sync a node from last checkpoint right now was working on friday, now it's much harder
I think also Prysm has a bug trying to serve payloads it doesn’t have
You can’t cap without a queue
the question is where the queue would be, yeah, CL or EL
The queue on the CL seems safe
But I just don’t think it solves the issue
whats the worst case? 1 valid followed by 1 invalid?
A few invalid in random places
But that is a very expensive attack
So that’s fine
The problem is valid ones
If all CL devs are fine with potentially thousands sig verifications per slot then I am fine to have no cap
We should just lower the gas limit 😅(jk)
is there a way to have the evm execute the builder deposits sig verification without a new deposit contract?
Get a flash loan
Reacted to "Get a flash loan" with 🤣
Reacted to "Get a flash loan" with 🤣
Reacted to "Get a flash loan" with 🤣
Reacted to "Get a flash loan" with 🤣
Cost for pairing should be about 1ms
could this pairing “job” not be paired somehow with the deposit itself?
Yeah if you batch, then you would essentially do a binary search to find the invalid signature, so logN number of pairings (worse case), where N is the size of the batch
Can we make a new contract which verifies this and then sends it to the original deposit contract?
Antwoord verzenden naar "Can we make a new ..." ah wait nvm if we still support sending to OG contract this defeats the purpose
Replying to "Can we make a new co..." thats a big change
Replying to "Can we make a new co..." We can, but the original contract can still be reached.
Replying to "Can we make a new co..." A jinx
Antwoord verzenden naar "Can we make a new ..." yeah throwing around random ideas 😅
Replying to "Can we make a new co..." A new contract that verifies for the builder as Barnabas suggested works
Heeft gereageerd op "We can, but the or..." met 👍
Heeft gereageerd op "thats a big change" met 🤠
Replying to "Can we make a new co..." But it’s not an easy change
Just throwing it out there but raising the min deposit also solves this 🙂
Heeft gereageerd op "A new contract tha..." met 👍
Heeft gereageerd op "Just throwing it o..." met 👍
Replying to "Just throwing it out..." not on devnets
Replying to "Just throwing it out..." we are rich on devnets/testnets
Replying to "Just throwing it out..." lol
@Parithosh Jayanthi are we talking about the gas limit issue?
That should be in the general part
Is Nico here?
Barnabas knows it too
Reacted to "Barnabas knows it too" with 👍
https://github.com/ethereum/pm/issues/2038#issuecomment-4420608861
Reacted to "Yeah if you batch, t..." with 👍
just for my understanding. The gas limit in the bid is the preference (what is configured using a flag) and not the +/- 1/1024 gas limit?
Well, ELs typically have flags for this
Replying to "Well, ELs typically ..." but they are static
EL then CL
I think
Replying to "just for my understanding. The gas limit in the bid is the preference (what is configured using a flag) and not the +/- 1/1024 gas limit?" The spec mentions that the limit in the bid is the same as the gas limit in the payload https://github.com/ethereum/consensus-specs/blob/031e521f0a82b0e475ecfc13f79dd251a6284fc2/specs/gloas/builder.md?plain=1#L125
Reacted to "EL then CL" with 👍
Reacted to "EL then CL" with 👍
Replying to "just for my understanding. The gas limit in the bid is the preference (what is configured using a flag) and not the +/- 1/1024 gas limit?" So i believe would be the current gas limit
Replying to "Cost for pairing sho..." This is in the case of single invalid signature but could be problematic in the scenario of many bad signatures
I assume the gas limit we pass over from the CL to the EL is still the preferred one and the EL takes care of the 1/1024 rule still
I agree with Marius
Heeft gereageerd op "I assume the gas l..." met 👍
we need to separate these 2 topics, 1) is about building the payload, and 2) is about who validates it (as potuz is saying)
why should the bid have the gas limit in it at all?
Replying to "why should the bid h..." you would want to select a payload that does what you configured your validator to do (increase or decrease it)
Replying to "why should the bid h..." send the bid in the proposer preferences, any bid over that proposer preference should be invalid no?
Are the proposer preferences updated everytime when a validator sets a new gas limit using the flag?
So CL target is hard constraint now?
It is now a constraint as well
We reject the builder’s header if it doesn’t give us something compatible
I don't understand what the el need to change now?
but who validates the calculated gas limit in gloas? @Potuz
Sgtm
Reacted to "Sgtm" with ❤️
Spicy
Barnabas the dictator
Reacted to "Barnabas the dictato..." with 😅
Replying to "but who validates th..." What validation Nico? The validation that it is compatible with the previous block is done by the EL
The EL should never use the value received through fcu for making the +/- 1/1024 rule stricter than it is. It should just be used for local building. But for validating, ELs shouldn't care up the gas limit going up or down, only that the 1/1024 rule is obeyed.
Replying to "but who validates th..." The validation that it was compatible with the preference should be in the CL
I there an EIP for BPO style @Barnabas ?
If we have to schedule an emergency gas limit downgrade then this is harder to do, so I dont think we should do BPO-like forks for this
Replying to "but who validates th..." but we are not passing the target gas limit to the EL during validation
Replying to "I there an EIP for B..." can make one
BPO-like forks have significant costs on the deployment/testing/etc side, due to needing new client releases or similar. BPOs are hardforks.
Reacted to "can make one" with 👍
Replying to "but who validates th..." The EL only validates 1559
Reacted to "Spicy" with 🌶️
Replying to "but who validates th..." We validate the compatibility with the target
Antwoord verzenden naar "If we have to sche..." I like simplifying the protocol but for now I do not think I like this idea
Replying to "but who validates th..." how can they do that without knowing what the target gas limit is?
Replying to "but who validates th..." That is my proposal
Replying to "but who validates th..." 1559 doesn’t care about the target only cares that the gas limit hasn’t changed that much
Replying to "but who validates th..." but how do you know if builder adhered to the proposers target gas limit then?
Don’t CLs do this target check against builder block already?
Choosing to continue on this topic in lieu of devnet scoping today. We can do devnet scoping async/on ACDC this week as a topic.
I think what Toni’s saying is my favorite, but it’s not clear if others in the CL want this
Replying to "Don’t CLs do this ta..." Yes we do
Replying to "Don’t CLs do this ta..." That’s why I think it should not be a contentious issue for us
Reacted to "That’s why I think i..." with 👍
there is a PR https://github.com/ethereum/execution-apis/pull/608
lol
You stick your head out, you get whacked
Reacted to "You stick your head out, you get whacked" with 😂
Reacted to You stick your head ... with "😂"
Reacted to "You stick your head out, you get whacked" with 😂
“Your reward for good work is more work”
Reacted to "You stick your head ..." with 😂
volunteering is non-optional
Reacted to "You stick your head out, you get whacked" with 😂
Reacted to "“Your reward for good work is more work”" with 😅
It’s in the EIP ( at least that’s what I copied )
gas limit bound defined by yellow paper
Reacted to "You stick your head ..." with 😂
Antwoord verzenden naar "gas limit bound de..." (part of protocol since chainstart / before EIP-1559)
I think this is also ok, but we shuld define the calculation in the CL spec in that case, it's a simple algorithm
Replying to "I think this is also..." Yeah, I can do that one if you want
We’re overtime, but choosing to continue today in case anyone wants to drop off!
I'm for the CL checking the increase/decrease and keep the EL only caring about 1/1024 (no matter of the direction)
Heeft gereageerd op "I'm for the CL che..." met 👍
I can draft that PR
Reacted to "I can draft that PR" with 👍
Reacted to "Yeah, I can do that ..." with 👍
Conditioned to Nico’s doing the engine API
Replying to "https://github.com/e..." https://ethereum-magicians.org/t/eip-xxxxx-gas-limit-schedule-gpo/28494
Antwoord verzenden naar "https://github.com..." wew this is fast
Replying to "https://github.com/e..." gpo ftw
Replying to "https://github.com/e..." Claude works fast
Replying to "https://github.com/e..." psst
Reacted to "Conditioned to Nico’..." with 😂
Reacted to "Conditioned to Nico’..." with 😂
Replying to "Conditioned to Nico’..." will do, don't worry, can you fix the devnet please
Reacted to "will do, don't worry, can you fix the devnet please" with 🤣
Reacted to "will do, don't worry..." with 🤣
Reacted to "will do, don't worry, can you fix the devnet please" with 🤣
Agenda
Close PR 5224 (SSZ limit raise); run DevNet <200M gas until progressive lists
Bid gas limit = target from preferences; payload gas limit = calculated
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.