Skip to content

Impossible to run op-node without EL p2p peers since 1.4.3 #16464

@zekchan

Description

@zekchan

Describe the bug

Run chain from superchain registry without peers for op-reth and getting


``` in op-node

### Steps to reproduce

1. start ghcr.io/paradigmxyz/op-reth:v1.4.3

--disable-discovery
--chain=ink

2. start op-node without ```  --syncmode=execution-layer ``` 



### Node logs

```text
t=2025-05-25T23:41:46+0000 lvl=warn msg="Deriver system is resetting" err="failed to find the L2 Heads to start from: failed to fetch current L2 forkchoice state: failed to find the L2 head block: failed to parse L1 info deposit tx from L2 block: data is unexpected length: 164"
t=2025-05-25T23:41:46+0000 lvl=warn msg="Deriver system is resetting" err="failed to find the L2 Heads to start from: failed to fetch current L2 forkchoice state: failed to find the L2 head block: failed to parse L1 info deposit tx from L2 block: data is unexpected length: 164"

Platform(s)

No response

Container Type

Docker

What version/commit are you on?

docker image ghcr.io/paradigmxyz/op-reth:v1.4.3
fe3653f

What database version are you on?

Local database version: 2

Which chain / network are you on?

ink

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-op-rethRelated to Optimism and op-rethC-bugAn unexpected or incorrect behaviorS-staleThis issue/PR is stale and will close with no further activity

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions