Document experimental disc v5 support

[alexandratran]

Description

Update CLI options, concepts, and guides, with information about experimental discovery v5 support.

Issue(s) fixed

Fixes #1920
Fixes #1928
Fixes #1930

Preview

• Configure P2P networking: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/how-to/connect/configure-ports#p2p-networking
• --bootnodes: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/reference/cli/options#bootnodes
• p2p options: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/reference/cli/options#p2p-host
• Specify a bootnode: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/private-networks/how-to/configure/bootnodes#specify-a-bootnode
• ENR URL: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/concepts/node-keys#enr-url
• Discovery genesis file item: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/reference/genesis-items#discovery-configuration-items
• admin_nodeInfo: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/reference/api#admin_nodeinfo
• --net-restrict: https://besu-docs-pb7tw7wf9-hyperledger.vercel.app/public-networks/reference/cli/options#net-restrict

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
besu-docs	Ready	Preview, Comment	Mar 27, 2026 3:59pm

[usmansaleem]

LGTM

[bgravenorst]

lgtm

[bgravenorst]

Is this related to https://github.com/besu-eth/besu-docs/pull/1926/changes ?

[usmansaleem]

Is this related to https://github.com/besu-eth/besu-docs/pull/1926/changes ?

It partially covers it. enr will be added, it doesn't replace enode in the admin_node.

I also responded to @alexandratran directly. Here is the discussion:

There are some additional cli options that we need to document along with this new "enr" changes, may be in a separate PR.

Regarding the current PR, one thing to note that the "enr" entries are only used if 'discovery v5" is enabled (as you mentioned in the "tip").

I need to come back to you regarding the --nat-method comment. The nat-method may not work with ipv6. In regards to discovery v5, we have started supporting dual-stack binding i.e. discovery library (udp) and rlpx service (tcp) can listen both on ipv4 and ipv6. However, with ipv6, the --nat-method is not tested (it is only meant to work with ipv4). If user specify --p2p-host=IPv6 Address, then --nat-method may not work or incorrectly override it.

Anyways, here is the cli help with new options:

P2P Discovery Options
...
      --bootnodes[=<enode://id@host:port>|<enr:base64Enr>[,<enode://id@host:port>|<enr:base64Enr>...]...]
                             Comma separated enode or ENR URLs for P2P discovery bootstrap. Must be either all enode URLs (discovery V4) or all
                               ENR URLs (discovery V5). Default is a predefined list.
      --p2p-host=<HOST>      IP address this node advertises to its peers (default: 127.0.0.1)
      --p2p-host-ipv6=<HOST> IPv6 address this node advertises to its peers (default: none)
      --p2p-interface=<HOST> Network interface address to listen on (default: 0.0.0.0)
      --p2p-interface-ipv6=<HOST>
                             IPv6 network interface address to listen on (default: none)
      --p2p-ipv6-outbound-enabled
                             Prefer IPv6 addresses for outbound P2P connections when peers advertise both IPv4 and IPv6.
                             When false (default), IPv4 is preferred.
                             If a peer only advertises one address family, it is always used.
                             (default: false)
      --p2p-port=<PORT>      Port on which to listen for P2P communication (default: 30303)
      --p2p-port-ipv6=<PORT> Port on which to listen for IPv6 P2P communication (default: 30404)
      ```

[usmansaleem]

nit: actually bootnodes can still take txt files or url as well, its just that they must either specify all enodes or all enrs (based on discovery v5 or v4).

[usmansaleem]

LGTM