Skip to content

why does geth client hard code 15 consensus layer boot nodes of discv5 protocol? #32813

@TayC710

Description

@TayC710

Ethereum geth client hard coded 15 consensus layer boot nodes of discv5 protocol, which is a design error. The geth client is an execution layer client. It should hard code the execution layer boot node of the discv5 protocol instead of the consensus layer boot node.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions