Skip to content

Conversation

@jm-clius
Copy link
Contributor

@jm-clius jm-clius commented Sep 29, 2025

(Messed up commit history here, so will squash before merging).

While investigating the scope of: #340 we found three reasons why a second milestone for mix may be needed. This will also allow us to close the basic lightpush milestone soon.

  • using discv5 discovery for mix is limited, as we reach the ENR size limit pretty soon (e.g. can't be used on fleet nodes)
  • using rendezvous discovery for mix is possible, but require modifying the nim-libp2p implementation and adding rendezvous support for js-waku
  • implementing js-mix in js-libp2p and subsequent integration in js-waku may introduce complexity risks too

For this reason I propose a second milestone to cover the discovery and js-waku work to improve mix use. At the same time we can add static configuration to allow the mix-for-lightpush milestone to be closed soon.

The addition of a static configuration task to the existing milestone also delayed its completion to beyond the initial expected 30 Sept due date, updated to 10 Oct.

WDYT @chaitanyaprem @fryorcraken?

@jm-clius jm-clius requested a review from chair28980 October 15, 2025 13:57
Copy link

@chaitanyaprem chaitanyaprem left a comment

Choose a reason for hiding this comment

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

LGTM, Thanks!

Copy link
Contributor

@fryorcraken fryorcraken left a comment

Choose a reason for hiding this comment

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

couple of comments, LGTM otherwise

@jm-clius jm-clius merged commit 7d2847d into master Oct 21, 2025
@jm-clius jm-clius deleted the feat/new-mix-milestone branch October 21, 2025 16:49
@fryorcraken
Copy link
Contributor

#291 (comment)

Please update commitment towards including mix in Waku API for js and nim

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.

5 participants