--- title: 'Mekong deprecation Announcement' date: '2025-03-06' author: Protocol Support Team category: Research & Development image: https://storage.googleapis.com/ethereum-hackmd/upload_b89ad13f2213a21c87b65e93b9219809.jpeg --- The [Mekong](https://blog.ethereum.org/2024/11/07/introducing-mekong-testnet) devnet was meant to be a playground for wallet developers to experiment with UX changes and for stakers to gain confidence in the upcoming [Pectra](https://eips.ethereum.org/EIPS/eip-7600) changes. The Pectra network upgrade has been activated on the Ethereum Sepolia and Holesky testnets. These networks can now be used to test the Pectra upgrade features. In light of this, we'd like to announce the deprecation of the Mekong testnet on 7th March, 2025. **Application and tooling developers are encouraged to use [Sepolia](https://github.com/eth-clients/sepolia)** to test applications, smart contracts, and other EVM functionality. Its permissioned validator set provides a stable test environment. Alternatively, many [local development environments](https://ethereum.org/en/developers/local-environment/) allow for testing against copies of the Ethereum mainnet state. **Stakers and infrastructure providers concerned with protocol-level testing are encouraged to wait for the [Holesky](https://github.com/eth-clients/holesky) testnet** to finalize, or to await an announcement on the Ethereum R&D discord for an alternate testing location. For validator setup testing, stakers should also consider the [Ephemery](https://github.com/ephemery-testnet/ephemery-resources) testnet. This network resets weekly and enables lightweight end-to-end testing of the validator lifecycle.
Last changed by  
 
parithosh.jayanthi@ethereum.org
702

Read more

Fusaka (EIP-7607) Retrospective - All Clients

Analysis Period: Sep 22, 2024 - Dec 22, 2025 Mainnet Activation: December 3, 2025 Prysm - Mainnet Fork Bug Post-mortems available: potuz's analysis Prysm team post-mortem Consensus Layer Clients

1/29/2026
Gas repricing workflow

flowchart TD Nums[Gas repricing in a doc] File[Script or Makefile] STEELRepo[STEEL<br/>repo<br/>PR with the title repricing] PitstopGeth[CI trigger on PR for pitstop geth<br/> branch called repricing/geth-repricing] STEELFill[STEEL<br/>fill using above branch <br/>repricing.tar.gz] PitstopAll[pitstop all<br/>client images] GABench[Gas<br/>benchmarker] Nums --> File

11/26/2025
How to create a shadowfork

Introduction: shadowfork Theory: General info: A chain consists of an Execution layer(EL) and a Consensus layer(CL) The EL is responsible for state (transactions, history, etc) and the CL is responsible for consensus (agreement on chain head) at a high level The EL is driven by the CL. i.e, The CL decides what the head of the chain is and the EL must accept that decision (mostly) The CL asks the EL to produce blocks, these blocks are placed in the EL chain as well as execution_payloads in the CL slot. This links the CL slot to the EL chain (leaving out caveats here) When the CL sends the request to produce a block, it also sends information about the block to build on top of

3/5/2025
Verkle transition

Considerations Resource use: CPU, Disk, Cost, I/O Syncing and Sync complexity increase Complexity of Implimentation and Testing Time for conversion to take place Ideological Methods Overview

1/18/2024
Read more from parithosh.jayanthi@ethereum.org
Published on HackMD