no peers ready to handle block requests for more P2P requests for L2 block history
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 36.5k
- Forks
- 643
- PR merge metrics
- No merged PRs in 30d
Description
I tried running the Ink Node following the tutorial, but I found that the static peers are often unstable, and the op-node is unable to find enough peers to sync the blocks.
- op-node: v1.10.2
- op-geth: v1.101411.4
- here is my op-node configuration:
- op-node
- --l1=<eth-address>
- --l1.beacon=<beacon-address>
- --l2=<op-get-address>
- --l2.jwt-secret=/var/data/geth/jwtsecret
- --rollup.config=/rollup.json
- --rpc.addr=0.0.0.0
- --rpc.port=7878
- --p2p.static=/ip4/34.32.193.134/tcp/9003/p2p/16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN
- --p2p.bootnodes=enr:-Iu4QCqTQZVBnbPWXcdUxcakGoCCzCFr5vVzDfNTOr-Pi3KaOJZMXlnqTR9r9p4EemXS8fS59EdQaX8qrkyE01nvsNcBgmlkgnY0gmlwhCIgwYaJc2VjcDI1NmsxoQMW3w0F1AibYelKqJUKaie5RuKc7S9sPfWvH4lSJw4Fo4N0Y3CCIyuDdWRwgiMs
- logs:
lvl=info msg="no peers ready to handle block requests for more P2P requests for L2 block history"
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.
Research direction
Start with the Ink Node tutorial and the supplied op-node configuration, then reproduce the reported synchronization log while checking the configured static peer and bootnode behavior. Done means the node can discover enough peers to handle L2 block-history requests and sync blocks reliably.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100