# verkle-gen-devnet-2 :::info :mega: verkle-gen in the devnet name means that the genesis state is a verkle state. There is no fork transition. ::: :::info :mega: In order to be able to sync up this network, you have to make sure that the **dencun** related code is **not** being triggered, as the current version of verkle is built on top of **shapella**. ::: :::info :mega: Verkle-genesis-Devnet-2 launched on 24th Nov 2023. This devnet shut down on the 2nd of Feb 2024. ::: :::info :mega: The legacy name of kaustinen-testnet has been dropped in favor of `verkle-devnet-x` and `verkle-gen-devnet-x`. `verkle-gen-devnet-x` begins at a verkle-genesis state. `verkle-devnet-x` begins at a shapella-genesis state, and goes through the fork transition. ::: ## EIP List for Verkle (EL) [EIP-4762: Statelessness gas cost changes](https://eips.ethereum.org/EIPS/eip-4762) - :heavy_check_mark: Active [EIP-6800: Ethereum state using a unified verkle tree](https://eips.ethereum.org/EIPS/eip-6800) - :heavy_check_mark: Active [EIP-7545: Verkle proof verification precompile](https://eips.ethereum.org/EIPS/eip-7545) - :exclamation: Not yet active on this devnet ## EIP List for Verkle (CL) [PR-3230: TheVerge: spec draft](https://github.com/ethereum/consensus-specs/pull/3230) :exclamation: Draft ## [Docker images](https://github.com/ethpandaops/verkle-devnets/blob/master/ansible/inventories/gen-devnet-2/group_vars/all/images.yaml) for devnet 2 ### Spec changes for verkle-gen-devnet-2 **Consensus Spec** - No additional change compared to kaustinen-testnet **Execution EIPs** - No additional change compared to kaustinen-testnet **Engine API** - No additional change compared to kaustinen-testnet **Beacon API** - No additional change compared to kaustinen-testnet **Builder Spec** - No additional change compared to kaustinen-testnet
Last changed by  
 
ethpandaops For the ethpandaops team, devops for EL/CL layers
519

Read more

fusaka-syncing-bugs

Here is a collection of overall bugs across devnet 3 and mainnet: Prysm: During the latest non finality, we had an issue when starting a node from a checkpoint with a pre-existing DB. (Starting from genesis was OK, and starting from a checkpoint with an empty DB was OK. This bug was possibly more likely to happen when the latest justified checkpoint was far away from the latest finalized checkpoint. (When, for example, we have a single checkpoint with > 2/3 participation). Teku:

9/15/2025
Untitled

bla

9/10/2025
Untitled

dd

9/9/2025
fusaka-devnet-5 spec

:::info :mega: fusaka-devnet-5 targets to launch on 10th of Sep 2025 and will shut off 7d later. ::: :::info We aim to test 1500 nodes on this testnet, using the same spec as devnet-3/4. ::: :::info We aim to use trunk branches of all clients!

9/9/2025
Read more from ethpandaops
Published on HackMD