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
Is your feature request related to a problem? Please describe.
Bootnodes for some Superchain members are already embedded in execution and consensus clients, but not all chains are reflected there. Bootnodes still have to be manually configured for most Superchain members, even when using the --network and --op-network flags for op-node and op-geth respectively.
Describe the solution you'd like
Add bootnodes to chains' configurations in the Superchain Registry, allowing execution and consensus clients to automatically configure bootnodes for any chain in the Registry.
Describe alternatives you've considered
I could submit PRs to op-geth, op-node, and other clients to add bootnodes for World Chain there, but that process must be repeated for any future EL/CL clients. Or I could manually configure the bootnode flags for the EL and CL clients, but wouldn't that defeat the purpose of the network flags mentioned earlier?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Bootnodes for some Superchain members are already embedded in execution and consensus clients, but not all chains are reflected there. Bootnodes still have to be manually configured for most Superchain members, even when using the
--network
and--op-network
flags forop-node
andop-geth
respectively.Describe the solution you'd like
Add bootnodes to chains' configurations in the Superchain Registry, allowing execution and consensus clients to automatically configure bootnodes for any chain in the Registry.
Describe alternatives you've considered
I could submit PRs to
op-geth
,op-node
, and other clients to add bootnodes for World Chain there, but that process must be repeated for any future EL/CL clients. Or I could manually configure the bootnode flags for the EL and CL clients, but wouldn't that defeat the purpose of thenetwork
flags mentioned earlier?The text was updated successfully, but these errors were encountered: