# fusaka-devnet-1 specs :::info :mega: fusaka-devnet-1 targets to launch on 9th June 2025 ::: :::info Meta EIP status tracker: https://notes.ethereum.org/@marioevz/fusaka-sfi-tracker ::: ### Changes include: - Data column sidecars by root - validator custody (optional) - distributed blob building - shifting cell proof computation to transaction sender ### Discussion: - Who is going to work on EELS/EEST for proof computation to tx sender? ## EIP List for fusaka-devnet-1 The list below links the specific commit versions of the EIPs included in devnet-1. [EIP-7594: PeerDAS - Peer Data Availability Sampling](https://github.com/ethereum/EIPs/blob/ed447a1105230659fdce084710ae36bc309ff99f/EIPS/eip-7594.md) [EIP-7823: Set upper bounds for MODEXP](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7823.md) [EIP-7825: Transaction Gas Limit Cap](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7825.md) :new: [EIP-7883: ModExp Gas Cost Increase](https://eips.ethereum.org/EIPS/eip-7883) [EIP-7892: Blob Parameter Only Hardforks](https://eips.ethereum.org/EIPS/eip-7892) ### Test Releases **Consensus Specs:** TODO **Exection Spec Tests:** TODO ### Spec versions required & Open PRs **Beacon Metrics** [PeerDAS metrics: add data column, kzg, custody metrics](https://github.com/ethereum/beacon-metrics/pull/14) Draft :grey_exclamation: **Beacon API** [`produceBlock` and `publishBlock`: Remove blobs and KZG proofs](https://github.com/ethereum/beacon-APIs/issues/519) Open :exclamation: **Builder Specs** **Consensus Specs** [Basic validator custody](https://github.com/ethereum/consensus-specs/pull/3871) Optional **Execution APIs** **Execution Spec PRs** **Execution Spec Tests PRs** [feat(tests): peerdas tracking issue](https://github.com/ethereum/execution-spec-tests/issues/1301) Open :exclamation: ### Validator custody | Client | Status | |------------|---------| | Teku | Supports with backfill | | Nimbus | Not yet supported | | Prysm | Supports without backfill | | Lighthouse | Not yet supported | | Grandine | Not yet supported | | Lodestar | Supports without backfill | ## Kurtosis Interop Conifg (Pre-devnet testing) ```yaml todo ``` ## Client Interop Readiness Manu's test scenarios: https://hackmd.io/@manunalepa/BJzNsCnvyx ### Prysm | Scenario | Grandine | Lighthouse | Lodestar | Nimbus | Prysm | Teku | | -------- | -------- | ---------- | -------- | ------ | ----- | ---- | | 1a | :question: | :question: | :question: | :question: | :question: | :question: | | 1b | :question: | :question: | :question: | :question: | :question: | :question: | | 2a| :question: | :question: | :question: | :question: | :question: | :question: | | 2b | :question: | :question: | :question: | :question: | :question: | :question: | | 3a | :question: | :question: | :question: | :question: | :question: | :question: | | 3b | :question: | :question: | :question: | :question: | :question: | :question: | | 4 | :question: | :question: | :question: | :question: | :question: | :question: | ## Reference spec for previous devnet: https://notes.ethereum.org/@ethpandaops/fusaka-devnet-0 ### Open future Questions: - Should fusaka-devnet-0 included [EIP-7892](https://github.com/ethereum/EIPs/pull/9423), BPO Hard Forks? - Alternately, should a pre-determined blob increase schedule triggered by a BPO mechanism (as proposed [here](https://hackmd.io/@ralexstokes/blob-acc-2025#Blob-schedule-for-Fusaka)) be included in fusaka-devnet-0?
Last changed by  
 
ethpandaops For the ethpandaops team, devops for EL/CL layers
48

Read more

fusaka-devnet-0 specs

:::info :mega: fusaka-devnet-0 targets to launch on 26th May 2025 ::: :::info :mega: fusaka-devnet-0 will have target/max blob 6/9 similar to pectra. Any bump in blob increase will be done via BPO in future devnets and not via max_blobs_per_block_fulu. ::: :::info :mega: bpo_1 will increase target/max blob 9/16 (?) 256 epochs after genesis. This will be followed by a bpo_2 which will decrease back to 6/9.

5/22/2025
peerdas-devnet-7 specs

:::info :mega: peerdas-devnet-7 targets launched on 9th May 2025 ::: :::info :mega: peerdas-devnet-7 will have target/max blob 6/9 similar to pectra. Any bump in blob increase will be done via BPO in future devnets and not via max_blobs_per_block_fulu. ::: Changes include: Data column sidecars by root

5/19/2025
Pectra mainnet checklist

[x] Contracts deployed on mainnet [x] Soak all client releases on bootnodes + EF infra [ ] Update our mainnet tooling [x] Releases checked with basic kurtosis + assertoor run with all tests[x] Investigate teku issues [x] MEV workflow on all clients [x] Run EEST release against kurtosis devnet [x] Mainnet shadowfork with mainnet releases

5/5/2025
eof-devnet-1

Reference spec for previous devnet: https://notes.ethereum.org/@ethpandaops/eof-devnet-0 Changed Align EOFCREATE stack args with EXTCALL #9503. Simplify EOFCREATE new address hashing scheme #9298. Change kind_data from 0x04 to 0xff #9502. Make container section size 4 bytes wide #9581. Modify max_stack_height of type section to be max_stack_increase #9600 #9656.

4/17/2025
Read more from ethpandaops
Published on HackMD