Fusaka: - blob-devnet-0 updates
Glamsterdam: - bal-devnet-2 updates - bal-devnet-3 readiness - epbs-devnet-0 implementation update - client readiness check
Gas limit:
- eth/70 implementation update
State bloat: - perf-devnet-3 updates
Gm
Hello
Gm
gm
gm
gm
Reacted to "Gm" with 🌞
Reacted to "gm" with 😎
Reacted to "gm" with ☀️
gm
Reacted to "Hello" with 🌞
ssz tests :)
Can also do it on empty state for pure compute ones
Benchmarkoor uses a snapshot so its not a live network. We can fill on Osaka and Glamsterdam
Reacted to "Benchmarkoor uses a ..." with 👍
Reacted to "Benchmarkoor uses a ..." with 👍
Replying to "Benchmarkoor uses a ..." Except for execute-remote dependent tests
today *
Antwoord verzenden naar "Benchmarkoor uses ..." This is a good point, I think it's there but I have to check that we can choose the fork to build these benchs on
Antwoord verzenden naar "https://github.com..." broken url :(
Replying to "https://github.com/e..." fixed
Replying to "https://github.com/e..." Trailing )
Heeft gereageerd op "fixed" met 🔥
Ship it?
Reacted to "Ship it?" with 👍
we haven't yet
very quiet audience 😂
Its optional, so its not a block
I listed on the spec sheet as optional
Reacted to "I listed on the spec..." with 👍🏽
Reacted to "very quiet audience ..." with 🍿
sorry again?
Reacted to "very quiet audience ..." with 🍿
Wen bal-devnet-3
Replying to "I listed on the spec..." https://notes.ethereum.org/@ethpandaops/bal-devnet-3
Reacted to "very quiet audience ..." with 🍿
We are working on a release today, afterwards we will be able to merge some stuff
Reacted to "We are working on a ..." with 🔥
And then create teh devnet-3 branch
Reacted to "We are working on a …" with 🔥
Replying to "Wen bal-devnet-3" EELS test release: https://github.com/ethereum/execution-spec-tests/releases/tag/bal@v5.2.0
Potuz: “we seem to be robust” Potuz: “we cannot sync”
Reacted to "Potuz: “we seem to b..." with 😂
Reacted to "Potuz: “we seem t..." with 😂
Reacted to "Potuz: “we seem to b..." with 😅
Reacted to "Potuz: “we seem to b..." with 😂
Reacted to "Potuz: “we seem to b..." with 😂
Heeft gereageerd op "Potuz: “we seem t..." met 😅
Replying to "Potuz: “we seem t..." this is fine
Should the payload ever arrive before the block? I guess we wouldn't expect this to happen in the happy path?
Reacted to "aljpc8.jpg" with 👀
Reacted to "aljpc8.jpg" with 👀
Reacted to "aljpc8.jpg" with 👀
we (Teku) have a delay of 500 ms after the block when we publish self built payload
Reacted to "aljpc8.jpg" with 👀
Reacted to "aljpc8.jpg" with 👀
Reacted to "Potuz: “we seem to b..." with 😂
@Stefan Bratanov what’s the branch? You can test against Prysm, it should handle early payloads
I can test against you guys if you do handle them
Reacted to "I can test against y..." with 🔥
teku is master
I need to merge one PR, then we can test
by the way we send and pack payload attestations in blocks, that's not issue for other clients right. they will be ignored for devnet-0? Just want to make sure it doesn't break clients
Replying to "I can test against y..." lodestar should be able to handle early payload
Reacted to "lodestar should be a..." with 🔥
kk thanks, I can turn it off easily if it causes issues on the gossip side when we run the devnets
Replying to "I can test against y..." Ah nice, what is the image I should use in Kurtosis to test against you guys?
Replying to "I can test against y..." ethpandops/lodestar:epbs-devnet-0
Reth is ready w/ eth70
Replying to "I can test against y..." Thanks will test today after I cleanup my open PRs
Reacted to "Thanks will test tod..." with 👍
we can include besu and reth today
Reacted to "Thanks will test tod..." with ❤️
Reacted to "we can include besu ..." with 🙏
Reacted to "we can include besu ..." with 🙏
nft-devnet-10
nethermind’s host is still being investigated for now
Can we hold off another day?
are we syncing reth in full or archive mode?
Can you guys share the logs with us?
Did Jenn not finish with it?
you should have access to the servers
Kk MB.
Ty @pk910
https://github.com/nerolation/state-actor LINK TO THE TOOL
FYI
What is the status of besu nodes on bloat network, I see that only geth is proposing blocks ? I’m trying to sync again from my side as a besu follower node but how about validator nodes ?
Replying to "What is the status o..." Will check now. Still, you should have access. All IPs to ssh are here: https://github.com/ethpandaops/perf-devnets/blob/master/ansible/inventories/devnet-3/inventory.ini
Reacted to "Will check now. Stil..." with 👍
Bloatnet covers main net compatibility, syncing testing
Heeft gereageerd op "Bloatnet covers ma..." met 👍
Rest can mostly be done with this tool
Like Geth’s Bintrie
Fusaka: - blob-devnet-0 updates
Glamsterdam: - bal-devnet-2 updates - bal-devnet-3 readiness - epbs-devnet-0 implementation update - client readiness check
Gas limit:
State bloat: - perf-devnet-3 updates
Skip expensive Blob DevNet; test Fusaka features on Holesky/Sepolia instead
Use dedicated CPU instances for 1-2 days on bal-devnet-2 for benchmarking
EPBS DevNet 0: stable network without sync/malicious testing initially
Payload attestations will be ignored in EPBS DevNet 0; not breaking clients
State Actor tool runs parallel to BloatNet for different testing purposes
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.