Skip to content

notices: op-geth deprecation #2171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
palango merged 3 commits into from
May 7, 2026
Merged

notices: op-geth deprecation #2171

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3203b6e
notices: op-geth deprecation
palango Apr 8, 2026
d3ad4c8
notices: update op-geth deprecation with upstream changes
palango May 5, 2026
5a35cc4
review
palango May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -407,6 +407,7 @@
{
"group": "Notices",
"pages": [
"infra-partners/notices/op-geth-deprecation",
"infra-partners/notices/req-resp-cl-sync-deprecation",
"infra-partners/notices/jovian-upgrade",
"infra-partners/notices/jello-upgrade",
Expand Down
33 changes: 33 additions & 0 deletions infra-partners/notices/op-geth-deprecation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: "op-geth Deprecation"
---

This notice outlines the deprecation of `op-geth` and the transition to `op-reth` as the supported execution client for Celo. It includes key information for node operators, RPC providers, and bridge operators.

`op-geth` will not support the upcoming Ethereum Glamsterdam hardfork. All node operators must migrate to `op-reth` before this upgrade to remain in sync with the canonical chain.

We will share exact dates once the Ethereum Glamsterdam timeline is finalized.

## Summary Of Changes

Following [Optimism's](https://docs.optimism.io/notices/op-geth-deprecation) deprecation of op-geth, Celo will also discontinue support for `op-geth` and adopt `op-reth` as the primary execution client.

- **`op-geth`**: Supported only until the Ethereum Glamsterdam hardfork. After this, it will no longer be compatible with the network.
- **`op-reth`**: The new supported execution client built on `reth`.
- **`op-node`**: No changes. It remains fully supported.

## Requirements for Node Operators

Node operators must complete migration to `op-reth` before the Ethereum Glamsterdam hardfork.

A Celo-compatible `op-reth` release and migration guide will be published shortly. In the meantime:

- Review `op-reth` and its configuration.
- Begin planning your migration timeline
- Monitor updates in the [celo-l2-node-docker-compose](https://github.com/celo-org/celo-l2-node-docker-compose) repository and this page for release details and instructions.

## RPC Providers and Bridge Operators

For most RPC users, this transition should be seamless. `op-reth` supports the same JSON-RPC interface as `op-geth`.

However, some differences may exist in non-standard or debug RPC methods. We recommend validating your integrations against `op-reth` once test environments are available.