Skip to content

Conversation

@anacrolix
Copy link
Contributor

This turns on discovery v5 by default.

It adds --discovery.v4 so you can also disable v4.

It prefers to use disc v5 for node resolution.

Most other changes are minimal changes from geth to maintain clean diff and updated behaviour around sources.

I expect there will be some rough edges but the sooner v5 is active in main the sooner those will come up.

Running with --discovery.v4=false might be worthwhile for testing, and maybe in some QA workflows.

@taratorio taratorio enabled auto-merge (squash) January 7, 2026 01:09
@taratorio taratorio merged commit 3ab406a into main Jan 7, 2026
18 checks passed
@taratorio taratorio deleted the anacrolix/discovery-v5 branch January 7, 2026 02:05
anacrolix added a commit that referenced this pull request Jan 13, 2026
This turns on discovery v5 by default.

It adds `--discovery.v4` so you can also disable v4.

It prefers to use disc v5 for node resolution.

Most other changes are minimal changes from geth to maintain clean diff
and updated behaviour around sources.

I expect there will be some rough edges but the sooner v5 is active in
main the sooner those will come up.

Running with `--discovery.v4=false` might be worthwhile for testing, and
maybe in some QA workflows.
AskAlexSharov pushed a commit that referenced this pull request Jan 13, 2026
Enables discv5 for 3.3 for
#18195. Duplicates #18578
from main.

I think we want discv5 enabled in 3.3 if we want to meet the Jan 31
target. I wonder if we want to keep the resolution leaning toward discv4
for 3.3.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants