Glamsterdam
Gas limit testing
- eth/70 updates
- benchmarking updates
- gas repricing update
- benchmarkoor demo
Zoom bot? 👀
Reacted to "Zoom bot? 👀" with 👀
my audio
does not work
sec
micdao
Reacted to "micdao" with ➕
Reacted to "micdao" with ➕
Reacted to "micdao" with ➕
Reacted to "micdao" with ➕
Stefan’s spec doc: https://notes.ethereum.org/@ethpandaops/bal-devnet-2
It should be present for non-finalized blocks though
a single malicous actor could trigger a chain to halt over 100M gas without eth/70
10MB still matters on CL gossip
yes 10MB is a hard limit right now
receipts are more problematic than block payloads >10M. a bigger block can't be broadcasted, but everyone generates the receipts themselves - except whenhitting sync
Call data price change is still important; because the size cap determining blocks rather than pricing distorts the gas market
What was the point about the ef making noises again? Sorry I missed the sentence
It should be tested, yes, but we wouldn't go to 150M gas without the calldata pricing adjustment. After the calldata increase we have (a lot of) leeway again before getting close to 10mib.
Want to call attention that fine control on the max size is also actually needed for ePBS because it will determine the max broadcast time allocated.
Replying to "What was the point a..." case in point :-) just kidding. he was talking about the suggestion that there might be a deadline for Glamsterdam, where even headliners that miss the deadline might be out
Reacted to "It should be tested,..." with 👍🏼
Reacted to "It should be teste..." with 👍🏼
Reacted to "It should be tested,..." with 👍🏼
Replying to "Want to call attenti..." Bc of the dynamic ptc deadline?
Reacted to "It should be tested,..." with 👍🏼
Replying to "What was the point a..." Ah yes, I think thats a good thing, no?
I would agree, it’s not clear why we should have this extra cap
Replying to "Want to call attenti..." yes, that seems to be a needed feature in this fork given the gas numbers that are being talked about
Reacted to "Want to call atten..." with 👍
Reacted to "It should be tested,..." with 👍🏼
Replying to "It should be tested,..." so what would you recommend for devnet-2 reduce to 100M?
Replying to "What was the point..." Not suggesting otherwise but saying it impacts BAL planning
Replying to "What was the point..." and means the existing overhead from Fusaka has to remain even though ePBS would remove most of it
Replying to "What was the point a..." Yep makes sense
Reacted to It should be tested,... with "👍🏼"
Replying to "It should be tested,..." 150M should be fine sice we have the rlp limit cap
Replying to "I would agree, it..." ok, but that's at the earliest an H* point
Replying to "It should be tested,..." Maybe not. Not sure anymore if 10mib is actually a problem ot not
Replying to "It should be tested,..." eth/70 is the missing part on going high (as mentioned receipts) https://eips.ethereum.org/EIPS/eip-7975
Replying to "I would agree, it’s ..." Sure, just saying I think that is the right way to do it eventually
Could we focus on testing bal instead of worrying about this high gaslimit scenario?
Reacted to "Could we focus on te..." with ➕
Reacted to "Could we focus on te..." with 👍🏼
Reacted to "Could we focus on te..." with ➕
Reacted to "Could we focus on ..." with ➕
Because there's another 10mib there?
Reacted to "Could we focus on ..." with ➕
Reacted to "Because there's anot..." with 👍
lest just decrease the gas cap to 70M and that should be safe enough to continue
True, put it to 100M and go with it
Reacted to "lest just decrease t..." with ➕
Reacted to "lest just decrease t..." with ➕
Reacted to "lest just decrease..." with ➕
Replying to "Could we focus on te..." This is about testing BALs
Replying to "It should be tested,..." Yeah, and is to allow receipt pagination
Reacted to Could we focus on te... with "➕"
Replying to "Could we focus on te..." So we would need calldata repricing for it
Reacted to So we would need cal... with "👍"
Geth miner limits blocks to ~7mb, transactions only
@Francesco any updates on the variable PTC deadline PR?
eth/70 I think we want to have live for Glamsterdam? So would test higher than 100M at somepoint to confirm that EIP is in and works
One thing I wanted to add to the prev discussion: please speed up implementation of eth/70 so we can go beyond 70mgas
what's max gas which fits in 10MB?
with repricings
Replying to "eth/70 I think we wa..." We are working on kurtosis tests to show it works
Replying to "eth/70 I think we wa..." Cc @pk910
We should get the beacon api prs merged in early this week
And update it with subsequent prs if needed, the discussions are too long and getting hidden
Oh is the safe limit 70 without it?
Replying to "One thing I wanted t..." Thought it was > 100M
Replying to "We should get the be..." working on it with Shane
For some reasons I can't raise hands so I'll leave it here the forkchoice change that is **needed* is to not be broken by empty slots
Reacted to "For some reasons I c..." with 👍
Replying to "One thing I wanted t..." I see 83 mgas on EIP-7975: eth/70
Replying to "We should get the be..." we will remove block production changes so we can discuss that separately and move ahead with the PR and merge it
we have a ethpandaops/geth:epbs-devnet-0
Reacted to "we will remove block..." with 👍
Reacted to "we have a ethpand..." with 👍
Reacted to "we have a ethpandao..." with 👍
Reacted to "we have a ethpandao..." with 👍
Replying to "One thing I wanted t..." Yeah 83
Reacted to "we have a ethpand..." with 👍
Replying to "we have a ethpand..." is this from some particular gh repo/branch?
Replying to "we have a ethpand..." or it is the gh org it looks like
Replying to "we have a ethpandao..." its a fork of mine
Replying to "we have a ethpandao..." I’ll check with marius if they can do an official upstream branch
Replying to "we have a ethpand..." that would be useful, not to rely on only a docker image
Replying to "Want to call attenti..." My current feeling is that it should just put as late into the slot as possible, ensuring max time for propagation while still ensuring our target gas limit can be executed (in the worst case) until the next slot.
@FLCL mind giving us an update?
sorry what was the question?
eth70
eth70
mic issues, no significant updates
Reacted to "mic issues, no signi..." with 👍🏼
We tried to test it and seems better to check it in a devnet
“Its working” “We are not sure why its working tho” 😂 oops
Reacted to "“Its working” “We ar..." with 😂
Reacted to "“Its working” “We ar..." with 😂
Could we just do eth70 for devnet 3?
Reacted to "“Its working” “We ar..." with 😂
Reacted to "Could we just do eth..." with 👀
Reacted to "Could we just do eth..." with 👍
Btw do you guys want to split only big receipts? Or anything that can be placed under size limit?
Reacted to "we have a ethpandao..." with 👍
Replying to "Could we just do eth..." Others will be able to sync with full sync only
Benchmark Release: https://github.com/ethereum/execution-spec-tests/releases/tag/benchmark%40v0.0.7 Benchmark Documentation: https://github.com/ethereum/execution-specs/blob/forks/amsterdam/docs/writing_tests/benchmarks.md
Replying to "Btw do you guys want..." We split only when a packet would exceed the size
https://github.com/misilva73/evm-gas-repricings/blob/main/reports/gas_repricings_todo.md
Replying to "https://github.com/m..." I will complete the eip-2780 benchmark today. wip
Guru is working on eip2780 spec right now, I am working on benchmark for it
Reacted to "Guru is working on e..." with 👍🏼
Reacted to "Guru is working on e..." with ❤️
Reacted to "Guru is working on..." with 👍🏼
+1 on 8037 on devnet-3
Replying to "+1 on 8037 on devnet..." I like this too
Replying to "+1 on 8037 on devnet..." Its the most complex one, so we should get it out of the way early
Replying to "+1 on 8037 on devnet..." me too we should discuss what we want to see in devnet-3 https://forkcast.org/devnets/
Reacted to "+1 on 8037 on devnet..." with 👀
Replying to "+1 on 8037 on devnet..." Will push in EELS, tests etc this week
Reacted to "Will push in EELS, t..." with 🔥
Replying to "+1 on 8037 on devnet..." 8037 is pretty large so maybe just that?
Reacted to "Will push in EELS, t..." with 🔥
Replying to "+1 on 8037 on devnet..." Who is the person that I can contact related to it?
Great logo 🔥
Reacted to "Great logo 🔥" with 🔥
Replying to "+1 on 8037 on devnet..." You can message me Dragan
Reacted to "Great logo 🔥" with 🔥
Replying to "+1 on 8037 on devnet..." Cool, will do that
Reacted to "Great logo 🔥" with 🔥
Reacted to "Great logo 🔥" with 🔥
8037 + the data repricings (7976, 7981), which have specs and aren't complex based on steel's assesment
Reacted to "Great logo 🔥" with 🔥
Would be great to get to testing higher gas limits without running into limits
Reacted to Great logo 🔥 with "🔥"
Reacted to "8037 + the data repr..." with 💯
Reacted to "Great logo 🔥" with 🔥
Reacted to +1 on 8037 on devnet... with "👍"
Reacted to "Great logo 🔥" with 🔥
This is great for EL performance benchmarking. Are you getting the results on all the runs or there is a way to have runs for warmup, and then use other runs for getting the metrics ?
Awesome work @Rafael Matias (skylenet) !!! 🎉
Reacted to "Awesome work @Rafael..." with 👏
Reacted to "Awesome work @Rafael..." with 👏
Amazing!!!
Reacted to "Awesome work @Rafael..." with 💯
Reacted to "Awesome work @Rafael..." with 👏
Reacted to "Awesome work @Rafa..." with 💯
Reacted to "Awesome work @Rafa..." with 👏
Reacted to "Awesome work @Rafael..." with 👏
beauty
Reacted to "Awesome work @Rafael..." with 👏
Reacted to "Awesome work @Rafael..." with 👏
And shoutout to @CPerezz ’s work on standardizing metrics. Super useful for folks wanted to analyze state operations
Reacted to "Awesome work @Rafael..." with 👏
Reacted to "And shoutout to @CPe..." with ❤️
Reacted to "And shoutout to @CPe..." with ❤️
Reacted to And shoutout to @CPe... with "❤️"
Reacted to Awesome work @Rafael... with "👏"
Reacted to "Awesome work @Rafa..." with 💯
Reacted to "Great logo 🔥" with 🔥
Reacted to "And shoutout to @CPe..." with ❤️
Reacted to "Awesome work @Rafael..." with 👏
Reduce bal-devnet-2 gas limit to 70M to focus on BAL testing
EPBS DevNet 0 will not test fork choice edge cases
ETH/70 should be tested in isolation before adding to BAL devnets
EIP-8037 (state growth) prioritized for DevNet 3 implementation
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.