End of Support for op-geth and transition to op-reth

Notice Date: April 16, 2026

Overview

GIWA Chain's execution client is transitioning from op-geth to op-reth. This transition follows the broader OP Stack ecosystem's shift in execution client support, with official support for op-geth ending on May 31, 2026.

Background

The OP Stack ecosystem is transitioning its execution client from op-geth (Go-based) to op-reth (Rust-based). After May 31, 2026, security patches and bug fixes for op-geth will be discontinued, and new feature development, including the upcoming Karst hardfork, will only be available on op-reth.

Additionally, the Fault Proof program is transitioning from op-program to kona-client (cannon-kona).

op-geth will not support the L1 Glamsterdam hardfork. Once Glamsterdam activates, nodes running op-geth will no longer be able to follow the canonical chain.

Key Changes

Component	Before	After	Note
Execution Client	op-geth	op-reth	End of support: May 31, 2026
Fault Proof Program	op-program	kona-client	Transition at Karst hardfork

For Node Operators

If you are running your own GIWA Chain node, you will need to migrate to op-reth before May 31, 2026.

1. Start syncing an op-reth node in parallel with your existing op-geth node.

2. Verify sync accuracy by comparing block hashes, state roots, and RPC outputs.

3. Once verified, migrate production traffic to op-reth.

For op-reth node setup, refer to the giwa-io/node repository. You can easily run an op-reth node using the CLIENT=reth option.

You can use snapshots to quickly set up an op-reth node without syncing from scratch.

For Developers

There is no impact on general DApp development. However, if you are connecting directly to a node RPC and using execution client-specific APIs, please verify compatibility with op-reth.

Learn More

Want to learn more about the execution client transition? Check out the OP Stack official notice.