RPC node fails to re-sync after sequencer migration
Open
@blockchaindevsh is already working on this.
Since Dec 2, 2025.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 1
Description
Reproduction steps:
- Launch a full node on the new sequencer machine and sync it to the latest block.
- Stop the current sequencer components (geth, op-node, batcher, proposer, and challenger).
- On the new sequencer machine, stop the full node and restart it using the sequencer configuration.
- Because the boot node and static node IDs have changed, stop the RPC node, update its boot node and static node configuration, and restart it. This whole process may take more than 30 minutes.
- After the restart, the RPC node fails to continue syncing
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.