implement discv5 handling

[macfarla]

Besu is currently using discv4.
Teku using discv5, via this repo https://github.com/Consensys/discovery
Besu is already importing those libraries but we aren't using discv5 yet.
Think geth supports discv5, unsure about other clients

https://github.com/ethereum/devp2p/blob/master/discv5/discv5.md

[KolbyML]

Hi @macfarla I think Samba's Team @Dsorken and @meldsun0 should be assigned this issue. Samba is the Java implementation of the Portal Network being integrated into Besu. Portal requires discv5. I am assuming you guys only want 1 instance of Discv5 being ran whether Samba is enabled or not.

So I am assuming this issue should be assigned to Samba instead of being given to the EPF https://github.com/eth-protocol-fellows/cohort-six/pull/7/files since Samba has to handle this issue in order to integrate Portal, and assigning this issue to the EPF could potentially block Samba and delay Discv5's integration into Besu.

Anyways I will let you and Samba's team continue the discussion. Let me know what you think 🫡

[meldsun0]

As @KolbyML mentioned, we’re currently integrating Samba as a plugin. At the moment, Samba runs with its own instance of Discv5. If there are plans to integrate Discv5 directly into Besu, I believe it’s important to ensure there’s only a single shared instance. Otherwise, enabling Samba as a plugin would result in two separate NodeRecords—one for Besu and one for Samba—which could lead to unnecessary complexity or conflicts.

That said, if this work is being assigned to the EPF, it might introduce blockers for us unless it's designed with the ongoing development of Samba in mind. I’d recommend further discussion to ensure alignment.

By the way, we've been actively working with the consensys/discovery library—suggesting changes and opening multiple issues to improve it.
We’re open to taking the initiative further down the road, but for now, our focus remains fully on Samba.

It would be helpful to understand the priority of this integration effort and what immediate benefits are expected, so we can better coordinate our efforts.

[GrapeBaBa]

@KolbyML @meldsun0 Haha, it's nice to see you guys here, we also have a project op-besu that needs discv5 support, and it's also based on the besu plugin mechanism, and hopefully this component can be depended on independently.

[pr9t]

@macfarla Could you please assign this issue to me?

[macfarla]

tracker https://notes.ethereum.org/@cskiraly/el-discovery-v5-tracker