Skip to content

Comments

Remove libp2p multiaddress #8683

Merged
mergify[bot] merged 8 commits intosigp:unstablefrom
jxs:remove-libp2p-multiaddress
Feb 9, 2026
Merged

Remove libp2p multiaddress #8683
mergify[bot] merged 8 commits intosigp:unstablefrom
jxs:remove-libp2p-multiaddress

Conversation

@jxs
Copy link
Member

@jxs jxs commented Jan 20, 2026

After a user reported on Discord reported having problems starting Lighthouse with discovery disabled and providing --boot-nodes
I noticed that when a bootnode is provided as ENR lighthouse connects to it directly using libp2p, when a bootnode is a multiaddress it needs to be a UDP multiaddress so that Lighthouse uses Discovery to fetch that node's ENR.
But then later when bootstrapping libp2p, Lighthouse tries to dial those multiaddresses directly from libp2p if they are TCP, thing is, they won't be, as that was not allowed when the config was parsed.
Lighthouse also supports libp2p-nodes config flag that dials the addresses provided in the same way as when providing a valid ENR.

This PR basically removes the --libp2p-nodes flag and uniforms on boot-nodes flag allowing users to pass TCP multiaddresses with the --boot-nodes flag

@jxs jxs requested review from ackintosh and dknopik January 20, 2026 17:45
@jxs jxs force-pushed the remove-libp2p-multiaddress branch from 694abe9 to 00b8194 Compare January 20, 2026 17:47
Copy link
Member

@ackintosh ackintosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jxs for the cleanup! ✨ Looks good to me.

One small thought: how about having a deprecation period for the --libp2p-nodes flag to preserve CLI compatibility? We usually do this for CLI changes -- keeping the old flag as an alias, emitting a warning when used ( e.g. the --logfile deprecation in #7723).

@ackintosh ackintosh added the ready-for-review The code is ready for review label Jan 21, 2026
Copy link
Member

@pawanjay176 pawanjay176 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks clean. I had no idea we accepted multiaddrs in boot-nodes as well.
Agree with @ackintosh about the deprecation instead of delete. I think some existing infra might depend on the flag.

…overy

  disabled

  - Filter multiaddrs to only those with UDP and P2P protocols required for discv5
  - Add warning when discovery is disabled but discv5-eligible boot-node multiaddrs
   are provided
@ackintosh
Copy link
Member

@jxs @pawanjay176 Also, I've filed a PR to improve the UX for the case where a user specifies a UDP multiaddr with --boot-nodes together with --disable-discovery. It would be great if you could take a look when you have some time.

jxs#6

…tosh

Filter boot-node multiaddrs for discv5 eligibility
Copy link
Member Author

@jxs jxs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed Akihito's suggestion and re-introduced the flag with deprecation notice, PTAL

@jxs jxs requested review from ackintosh and pawanjay176 January 29, 2026 12:29
@jxs jxs force-pushed the remove-libp2p-multiaddress branch from 83fd1cd to f1b1b81 Compare January 29, 2026 12:46
Copy link
Member

@ackintosh ackintosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jxs!

jxs and others added 3 commits February 9, 2026 15:41
Co-authored-by: Akihito Nakano <sora.akatsuki@gmail.com>
Co-authored-by: Akihito Nakano <sora.akatsuki@gmail.com>
Co-authored-by: Akihito Nakano <sora.akatsuki@gmail.com>
@jxs jxs requested a review from ackintosh February 9, 2026 15:42
@mergify
Copy link

mergify bot commented Feb 9, 2026

Some required checks have failed. Could you please take a look @jxs? 🙏

@mergify mergify bot added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-review The code is ready for review labels Feb 9, 2026
Copy link
Member

@ackintosh ackintosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@jxs jxs added ready-for-merge This PR is ready to merge. and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Feb 9, 2026
@mergify mergify bot added the queued label Feb 9, 2026
@mergify
Copy link

mergify bot commented Feb 9, 2026

Merge Queue Status

Rule: default


This pull request spent 13 minutes 18 seconds in the queue, with no time running CI.

Required conditions to merge
  • check-success=local-testnet-success
  • check-success=test-suite-success

Reason

Pull request #8683 has been dequeued by a dequeue command

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

mergify bot added a commit that referenced this pull request Feb 9, 2026
@michaelsproul
Copy link
Member

@mergify dequeue

@mergify
Copy link

mergify bot commented Feb 9, 2026

dequeue

✅ The pull request has been removed from the queue

@michaelsproul
Copy link
Member

Just quickly dequeueing so I can merge another PR which bypasses mergify:

Looks like CI for the book might also be failing?

@michaelsproul michaelsproul added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-merge This PR is ready to merge. labels Feb 9, 2026
@mergify mergify bot added dequeued and removed queued labels Feb 9, 2026
@jxs
Copy link
Member Author

jxs commented Feb 9, 2026

Just quickly dequeueing so I can merge another PR which bypasses mergify:

Looks like CI for the book might also be failing?

yup, thanks Michael. Addressed

@mergify mergify bot removed the dequeued label Feb 9, 2026
@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Feb 9, 2026
@michaelsproul
Copy link
Member

@mergify queue

@mergify
Copy link

mergify bot commented Feb 9, 2026

queue

✅ The pull request has been merged automatically

Details

The pull request has been merged automatically at 0c9f97f

@mergify
Copy link

mergify bot commented Feb 9, 2026

Merge Queue Status

Rule: default


This pull request spent 32 minutes 49 seconds in the queue, including 30 minutes 57 seconds running CI.

Required conditions to merge
  • check-success=local-testnet-success
  • check-success=test-suite-success

@mergify mergify bot added the queued label Feb 9, 2026
@michaelsproul michaelsproul added the backwards-incompat Backwards-incompatible API change label Feb 9, 2026
mergify bot added a commit that referenced this pull request Feb 9, 2026
@mergify mergify bot merged commit 0c9f97f into sigp:unstable Feb 9, 2026
36 of 37 checks passed
@mergify mergify bot removed the queued label Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompat Backwards-incompatible API change ready-for-merge This PR is ready to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants