Skip to content

[Do not merge] net/discovery: Remove legacy /kad protocol#6109

Closed
lexnv wants to merge 10 commits intomasterfrom
lexnv/disable-legacy-kad
Closed

[Do not merge] net/discovery: Remove legacy /kad protocol#6109
lexnv wants to merge 10 commits intomasterfrom
lexnv/disable-legacy-kad

Conversation

@lexnv
Copy link
Copy Markdown
Contributor

@lexnv lexnv commented Oct 17, 2024

This PR removes the legacy /kad kademlia protocol.

Instead, nodes use the genesis based kademlia protocol for the discovery process.

Part of:

cc @paritytech/networking

lexnv added 5 commits October 17, 2024 12:54
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv added T0-node This PR/Issue is related to the topic “node”. I5-enhancement An additional feature request. labels Oct 17, 2024
@lexnv lexnv self-assigned this Oct 17, 2024
lexnv and others added 5 commits October 17, 2024 13:23
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@skunert
Copy link
Copy Markdown
Contributor

skunert commented Oct 17, 2024

From reading the issue #504 it is not 100% clear to me if this is now safe to remove? Do all nodes need to run #3833 for it to be safe?

@lexnv
Copy link
Copy Markdown
Contributor Author

lexnv commented Oct 17, 2024

Do all nodes need to run #3833 for it to be safe?

Yep that's a good point. Will crawl the DHTs and see if someone is still running legacy only kademlia, meanwhile will add a Do not merge on this pr

@lexnv lexnv changed the title net/discovery: Remove legacy /kad protocol [Do not merge] net/discovery: Remove legacy /kad protocol Oct 17, 2024
@nazar-pc
Copy link
Copy Markdown
Contributor

This is needed for libp2p 0.54 upgrade that to not use deprecated features

@lexnv
Copy link
Copy Markdown
Contributor Author

lexnv commented Jan 30, 2026

No longer needed, will reconsider in the future

@lexnv lexnv closed this Jan 30, 2026
@kayabaNerve
Copy link
Copy Markdown

As context, may I ask if there's a superseding issue/PR/design decision which makes this no longer needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

I5-enhancement An additional feature request. T0-node This PR/Issue is related to the topic “node”.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants