[Node Operator Question] Optimism Sepolia bootnodes (op-node / op-reth client stack)

[StevenMartinez94]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm trying to run an archival Optimism Sepolia node using the op-node + op-reth. Right now i'm having a hard time trying to find peers, can anyone share a RETH compatible bootnode list?

Steps to Reproduce

You can reproduce my docker-compose environment here -> https://gist.github.com/StevenMartinez94/43c153b4bd4aa40c6e3f98ecca428cc0

Which component is affected?

• op-geth
• op-node
• Other

Expected vs. Actual Behavior

In a expected behaviour (in a case i would get peers/bootnodes) my execution layer would give me logs like:
optimism-sepolia-reth-node | 2025-05-19T19:18:25.366009Z INFO Status connected_peers={NUMBER_OF_PEERS} latest_block=27656730 instead of optimism-sepolia-reth-node | 2025-05-19T19:18:25.366009Z INFO Status connected_peers=0 latest_block=27656730.

Environment Details

OS: Ubuntu 24.04.1 LTS
HARDWARE:
--- CPU: AMD EPYC 9354P (64) @ 3.250GHz
--- RAM: 377 GB

Protocol Information

Most of protocol information can be found here -> https://gist.github.com/StevenMartinez94/43c153b4bd4aa40c6e3f98ecca428cc0

op-reth docker image: ghcr.io/paradigmxyz/op-reth
op-node docker image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.2
network name: Optimism Sepolia
chain id:
---l2_chain_id=11155420
---l2_network=op
---l1_chain_id=11155111
---l1_network=sepolia
L1 chain: ETH Sepolia (erigon v3 client)

Node Logs

INFO Status connected_peers=0 latest_block=27656730

Troubleshooting Attempts

No response

Additional Information

No response

Feedback

No response

[jsvisa]

Maybe you can try the below bootnodes from https://github.com/paradigmxyz/reth/blob/main/crates/net/peers/src/bootnodes/optimism.rs#L21-L34

/// OP stack testnet boot nodes.
pub static OP_TESTNET_BOOTNODES: &[&str] = &[
    // OP Labs
    "enode://2bd2e657bb3c8efffb8ff6db9071d9eb7be70d7c6d7d980ff80fc93b2629675c5f750bc0a5ef27cd788c2e491b8795a7e9a4a6e72178c14acc6753c0e5d77ae4@34.65.205.244:30305",
    "enode://db8e1cab24624cc62fc35dbb9e481b88a9ef0116114cd6e41034c55b5b4f18755983819252333509bd8e25f6b12aadd6465710cd2e956558faf17672cce7551f@34.65.173.88:30305",
    "enode://bfda2e0110cfd0f4c9f7aa5bf5ec66e6bd18f71a2db028d36b8bf8b0d6fdb03125c1606a6017b31311d96a36f5ef7e1ad11604d7a166745e6075a715dfa67f8a@34.65.229.245:30305",
    // Base
    "enode://548f715f3fc388a7c917ba644a2f16270f1ede48a5d88a4d14ea287cc916068363f3092e39936f1a3e7885198bef0e5af951f1d7b1041ce8ba4010917777e71f@18.210.176.114:30301",
    "enode://6f10052847a966a725c9f4adf6716f9141155b99a0fb487fea3f51498f4c2a2cb8d534e680ee678f9447db85b93ff7c74562762c3714783a7233ac448603b25f@107.21.251.55:30301",
    // Uniswap Labs
    "enode://9e138a8ec4291c4f2fe5851aaee44fc73ae67da87fb26b75e3b94183c7ffc15b2795afc816b0aa084151b95b3a3553f1cd0d1e9dd134dcf059a84d4e0b429afc@3.146.117.118:30303",
    "enode://34d87d649e5c58a17a43c1d59900a2020bd82d5b12ea39467c3366bee2946aaa9c759c77ede61089624691291fb2129eeb2a47687b50e2463188c78e1f738cf2@52.15.54.8:30303",
    "enode://c2405194166fe2c0e6c61ee469745fed1a6802f51c8fc39e1c78c21c9a6a15a7c55304f09ee37e430da9a1ce8117ca085263c6b0f474f6946811e398347611ef@3.146.213.65:30303",
];

[StevenMartinez94]

Thanks for your reply. I have already tried with those OP LABS testnet bootnodes earlier but it didn't helped. That's why I'm not sure if bootnodes who run GETH client also do the trick for RETH client nodes.

[jsvisa]

INFO Status connected_peers=0 latest_block=27656730

Besides of this log, does your local op-reth node's db growing?

[opfocus]

Please do more observation to see if this does not affect your node synchronization

[opfocus]

[opfocus]

I tested running an op-reth node, and as shown in the screenshot above, it is working properly. I followed the documentation "Running Reth on OP Stack chains". Although the documentation doesn't use Docker, I believe that shouldn’t make much of a difference.

[opfocus]

I'll temporarily close this issue, but you can still add comments in this discussion.