Devnet status updates
- Updates on glamsterdam-devnet-7
- Glamsterdam-devnet-8
Discussions
- Hegota branching discussion: https://github.com/ethereum/pm/issues/2170#issuecomment-5091098854
Gm
gm
Tysm scenarios are going on, right now epbs mutator flips bits in the bids and propagates them on the network
Next one will perform targeted PTC vote drops
https://discord.com/channels/595666850260713488/892088344438255616/1529440070908510308
we might have some bid propagation issues
we are investigating
that seems hard to know without more info, we will take that bid unless the circuit breaker is active
you take the bid even if local is higher?
do you do any basic comparison in the value?
no, but Stefan said the bid is really high value
With circuit breaker then you’d local build anyway right? Even if the bid is high
Is the gas computation correct?
Is the bid building on the right head?
If the head changes last sec then
That’s the main suspect to not taking it
Anyway prysm logs should be clear why we ignore such bid
Replying to "With circuit breaker..." yes with circuit breaker active we only use local payloads
Reacted to "Anyway prysm logs should be clear why we ignore such bid" with 👍
lodestar should alos have a debug log for this
Yeah please let us know what the log line looks like, just something with “circuit breaker live” in it?
Replying to "Yeah please let us k..." there is a log for that too
Reacted to "there is a log for that too" with ❤️
We will add optimizations to devnet-7 today
I need to check with the other people on the team working on performance
Replying to "Yeah please let us k..." it's a warning log as following: "Builder circuit breaker activated, ignoring builder bids"
(Teku) We are merging a lot of bid reprocessing improvements today/tomorrow, it will also add debug logging with reasons
Reacted to "it's a warning log as following: "Builder circuit breaker activated, ignoring builder bids"" with ❤️
Replying to "Yeah please let us k..." (Teku) LOG.debug( "Builder circuit breaker engaged: slot:
https://notes.ethereum.org/@ethpandaops/glamsterdam-devnet-8
EELS: https://github.com/ethereum/execution-specs/issues/3167
Could we get an update on the builder API?
That was a big change afaik
Reacted to "That was a big chang..." with 👍
Reacted to "That was a big change afaik" with 👍
Reacted to "That was a big cha..." with 👍
Reacted to "Could we get an upda..." with ➕
Reacted to "That was a big change afaik" with 👍
Regarding the Besu performance improvements: The changes we tested today and needed to roll back should be the last ones. We just need to fix the bugs those improvements have introduced and then merge them again into our devnet branch
Reacted to "That was a big chang..." with 👍
Reacted to "EELS: https://github..." with 👍
0 consensus changes and also optional
Reacted to "Regarding the Besu p..." with 👍
Reacted to "0 consensus changes ..." with 👍
Replying to "0 consensus changes ..." If it were critical (to the core protocol) it would be included in consensus-specs 🙂
Reacted to "If it were critical ..." with 👍
Do we need repricing numbers for devnet 8?
Updates^^
The CL specs team will make an alpha.13 release for devnet-8 by the end of this week.
Replying to "The CL specs team wi..." Hopefully mid-week.
Do we need benchmarks for final numbers on devnet-8? Is devnet-7 enough?
We also need the optimizations
lets revisit devnet-8 launch date on ACDT next week?
https://github.com/ethereum/pm/issues/2170#issuecomment-5091899084
That’s Bosul from the networking team 🙂
Reacted to "That’s Bosul from the networking team 🙂" with 🙏🏼
Reacted to "That’s Bosul from the networking team 🙂" with ❤️
I think if we intend to ship this for Glamsterdam, we should have it in a devnet
Replying to "I think if we inte..." Big agree!
Reacted to "I think if we intend to ship this for Glamsterdam, we should have it in a devnet" with 👍🏼
Reacted to "Big agree!" with 👍🏼
Reacted to "I think if we intend..." with 👍🏼
Reacted to "I think if we intend..." with 👍🏼
imo this is a non priority: https://dune.com/queries/3757544/6319515 Would propose delaying it to h*. Most CL clients don’t have the partial cells implementation complete yet, so this is a major lift for them.
What timelines are we looking at with this?
whats the point of the engine api if the feature is not there?
Replying to "whats the point of..." do you mean partial data columns or sparse blobpool?
Replying to "What timelines are w..." Launch alongside devnet-8 is what I understand
Replying to "whats the point of t..." isn’t partial data columns a prerequisite for sparse blobpool?
Replying to "whats the point of..." no, both have benefits by themselves afaik
for Besu should be fine to implement only Engine API part
Reacted to no, both have benefi... with "👍"
Reacted to "no, both have benefits by themselves afaik" with 👍
Maybe worth going client to client?
Reacted to "Maybe worth going client to client?" with 👍🏼
Replying to "whats the point of t..." okay so one could have sparse blobpool implementation but have 0 partial data column impl?
No problem on our side
Replying to "whats the point of t..." ^ yes it is possible
IMO, for getBlobsV4 it is fine to not support it as it is gated by capability. I am just worried about only some clients understanding the custody_columns parameter in fcu
We have engine api tests in EELS for this - thanks to Louis (that we can run in hive), Geth is passing all of them (with small change), have vibed it in Nethermind too (all passing)!
Nethermind is good; have PR for it
Reacted to "Nethermind is good..." with 🔥
Reacted to "Nethermind is good; ..." with 🔥
Yeah, reth already have it merged on main
Reacted to "Yeah, reth already..." with 🔥
I’m not sure. I’d need to look into it.
LH has PRs ready to go
Reacted to "LH has PRs ready to go" with 🙏🏼
where is the execution api pr for this btw?
Are we using fcuV3 atm on the devnets? Or fcuV4 without the custody field
Replying to "where is the executi..." https://github.com/ethereum/execution-apis/pull/774
lighthouse still uses fcuV3 and only fcuV4 when they are proposers
Ohh man I should’ve followed this discussion, it doesn’t make any sense to send this on FCU
Reacted to "https://github.com/ethereum/execution-apis/pull/774" with 🙏🏼
Nethermind already running sparse blob pool in devnet-7
Yep, its optional
personally, i also would prefer a separate call, but do not feel tooo strongly about it
(especally because we are quite ahead)
call as in RPC method
Reacted to "call as in RPC met..." with 📞
Reacted to "call as in RPC method" with 📞
https://ethereumfoundation.zoom.us/j/89441658268?pwd=yjqf4TheEb1R7ZSuesCdOAy5tdyVk7.1
Reacted to "https://ethereumfoundation.zoom.us/j/89441658268?pwd=yjqf4TheEb1R7ZSuesCdOAy5tdyVk7.1" with 🫡
Reacted to "https://ethereumfoundation.zoom.us/j/89441658268?pwd=yjqf4TheEb1R7ZSuesCdOAy5tdyVk7.1" with 🫡
Reacted to "https://ethereumfoun..." with 🫡
@spencer do you know if there’s a specs PR for this?
Replying to "@spencer do you kn..." Guru's PR: https://github.com/ethereum/execution-specs/pull/3214
Replying to "https://github.com..." EELS PR: https://github.com/ethereum/execution-specs/pull/3238
I also don’t want to hang on in naming issues 😅 so fine for me, just a nit
Reacted to "I also don’t want to hang on in naming issues 😅 so fine for me, just a nit" with 😂
It is hard to name it as it covers both execution and block bytes/size. Execution gas sgtm, it is nicer.
Antwoord verzenden naar "I also don’t want..."
)
Heeft gereageerd op "It is hard to name..." met ❤️
Reacted to "from a software po..." with 💯
Reacted to "It is hard to name it as it covers both execution and block bytes/size. Execution gas sgtm, it is nicer." with ❤️
Reacted to "It is hard to name it as it covers both execution and block bytes/size. Execution gas sgtm, it is nicer." with 👍
Reacted to "It is hard to name..." with ❤️
Sorry didn’t read it before the call
I don’t think this affects zkVM
The EIP now says; If the chain is already running with gas parameters that no longer allow deployment via the keyless transaction, the only way to add the contract at the expected address is a coordinated irregular state transition, which is outside the scope of this EIP. Client software MUST NOT check for the existence of the contract at the fork boundary. I think this is fine and we should not change
pari has advocated for chaos/adversarial testing on a devnet 9. not sure the impact on testnet scheduling
EIP-8070 Engine API changes (GetBlobsV3/V4, FCU custody_columns) are mandatory for devnet-8; cell-level DAS deferred
EIP-2780 log cost simplification included in devnet-8 with no objections
EIP-8037 rename 'regular gas' to 'execution gas' included in devnet-8 with no objections
EIP-7997: close both open PRs; existing spec text is correct — no BAL read or contract check at fork boundary
devnet-8 launch date deferred; to be revisited at next ACDT once repricing numbers are available
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.