# peerdas-devnet-6 specs :::info :mega: peerdas-devnet-6 targets launched on 9th April 2025 ::: :::info :mega: Note: PeerDAS is activated at the `FULU_FORK_EPOCH` ::: ### Changes include: - validator custody - 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 peerdas-devnet-6 The list below links the specific commit versions of the EIPs included in devnet-6. [EIP-7594: PeerDAS - Peer Data Availability Sampling](https://github.com/ethereum/EIPs/blob/ed447a1105230659fdce084710ae36bc309ff99f/EIPS/eip-7594.md) ### Test Releases **Consensus Specs:** [v1.5.0-beta.4](https://github.com/ethereum/consensus-specs/releases/tag/v1.5.0-beta.4) **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** [Add EIP-7594 (PeerDAS) related changes](https://github.com/ethereum/beacon-APIs/pull/516) Merged :heavy_check_mark: [`produceBlock` and `publishBlock`: Remove blobs and KZG proofs](https://github.com/ethereum/beacon-APIs/issues/519) Open :exclamation: **Builder Specs** [Add EIP-7594 (PeerDAS) related changes](https://github.com/ethereum/builder-specs/pull/117) Open :exclamation: **Consensus Specs** [Basic validator custody](https://github.com/ethereum/consensus-specs/pull/3871) Merged :heavy_check_mark: ~~[make validator custody static for beacon node run session](https://github.com/ethereum/consensus-specs/pull/4154) Closed:x:~~ [Add Distributed Blob Publishing to Fulu networking spec](https://github.com/ethereum/consensus-specs/pull/4183) Merged :heavy_check_mark: [Update BlobsBundle for Fulu](https://github.com/ethereum/consensus-specs/pull/4187) Merged :heavy_check_mark: [Add note about using `getBlobs` with `DataColumnSidecar` in Fulu](https://github.com/ethereum/consensus-specs/issues/4186) Resolved :heavy_check_mark: [Transition period from 4844-style blob transactions to PeerDAS-style blob transactions](https://github.com/ethereum/consensus-specs/issues/4232) Open :exclamation: **Execution APIs** [Add EIP-7594 (PeerDAS) related changes](https://github.com/ethereum/execution-apis/pull/630) Open :exclamation: **Execution Spec PRs** [More post Prague re-factors](https://github.com/ethereum/execution-specs/pull/1159) Draft :grey_exclamation: **Execution Spec Tests PRs** [feat(tests): peerdas tracking issue](https://github.com/ethereum/execution-spec-tests/issues/1301) Open :exclamation: ## Kurtosis Interop Conifg (Pre-devnet testing) ```yaml participants_matrix: el: - el_type: nethermind el_image: ethpandaops/nethermind:feature-peerdas - el_type: reth el_image: ethpandaops/reth:rkrasiuk-peerdas - el_type: geth el_image: ethpandaops/geth:marius-engine-getblobs-v2 cl: - cl_type: lighthouse cl_image: ethpandaops/lighthouse:peerdas-devnet-6 supernode: true - cl_type: lighthouse cl_image: ethpandaops/lighthouse:peerdas-devnet-6 supernode: false - cl_type: grandine cl_image: ethpandaops/grandine:hangleang-peerdas-devnet-6 supernode: true - cl_type: grandine cl_image: ethpandaops/grandine:hangleang-peerdas-devnet-6 supernode: false network_params: electra_fork_epoch: 0 fulu_fork_epoch: 1 max_blobs_per_block_fulu: 64 target_blobs_per_block_fulu: 48 additional_services: - dora - spamoor_blob ``` ## 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/peerdas-devnet-5 ### Open future Questions: - Should peerdas-devnet-7 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 peerdas-devnet-7?