You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Placeholder. First need to gather requirements from Interop and Proofs, then come up with right db format. Is op-node's format still good?
Current implementation tracking
This issue is the feature-parity index for SafeDB under ethereum-optimism/protocol-team#49. The earlier placeholder above is historical.
The implementation and its acceptance criteria are consolidated in #23473 and its existing sub-issues #23474 through #23481. That breakdown supersedes the implementation scope in #22528; no parallel SafeDB implementation is required here.
The safe-head RPC previously tracked by ethereum-optimism/protocol-team#417 is covered by #23475. The super-root RPC implementation is covered by #23476, with the existing feature requirement in #21861.
Checkpoint recovery (ethereum-optimism/protocol-team#328) is tracked under reliability. The mixed-client devnet (ethereum-optimism/protocol-team#283) is tracked under rollout. SafeDB remains a prerequisite for adding proposer/challenger validation to that devnet, not the parent of the entire devnet or conductor workstream.
This needs to work well with interop and proofs. But also, we don't want to just blindly adopt what op-node did without considering some better designs.
I took a jab at this, based on the design document. The branch is more of a preview to make it more concrete. In interest of progress, I started with a 1-to-1 copy by defining a trait SafeDBv1, and then we can add a SafeDBv2 where we can experiment with the interface and and implementation.
Superseded by #23473, which is the canonical SafeDB implementation and feature-parity tracker under ethereum-optimism/protocol-team#49.
The remaining historical Interop/Proofs design context has been preserved in a comment on #23473. No separate SafeDB implementation scope remains here. Both issues already have the same Start date (2026-10-15) and Target date (2026-10-29).
The redundant sub-issue link from ethereum-optimism/protocol-team#49 is being removed; #23473 remains directly linked there.
Activity
geoknee commentedon Jun 18, 2026
This needs to work well with interop and proofs. But also, we don't want to just blindly adopt what op-node did without considering some better designs.
einar-oplabs commentedon Jun 23, 2026
I took a jab at this, based on the design document. The branch is more of a preview to make it more concrete. In interest of progress, I started with a 1-to-1 copy by defining a trait
SafeDBv1, and then we can add aSafeDBv2where we can experiment with the interface and and implementation.einar-oplabs commentedon Oct 26, 2026
Superseded by #23473, which is the canonical SafeDB implementation and feature-parity tracker under ethereum-optimism/protocol-team#49.
The remaining historical Interop/Proofs design context has been preserved in a comment on #23473. No separate SafeDB implementation scope remains here. Both issues already have the same Start date (2026-10-15) and Target date (2026-10-29).
The redundant sub-issue link from ethereum-optimism/protocol-team#49 is being removed; #23473 remains directly linked there.