-
Notifications
You must be signed in to change notification settings - Fork 3
mix implementation and integration in js #340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
jm-clius
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor comments
Co-authored-by: fryorcraken <[email protected]>
c7020bc to
2ce478b
Compare
| # Introduce Mixnet For Message Sending | ||
|
|
||
| **Estimated date of completion**: 30 Sep 2025 | ||
| **Estimated date of completion**: TBD(As it requires further study and analysis to determine estimate of new changes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chaitanyaprem can you fix the TBD so we can plan/merge :)
|
@fryorcraken after conversation with @chaitanyaprem I propose that we close this PR without merging. Initial estimate is that js-waku support would take another 3 months. Furthermore, discovery is also more complex than expected - we run into ENR size limits sooner than expected and temporaruy alternatives (like rendezvous) has its own complexities. I've opened another PR that suggests adding a second milestone so we can close this one: #362 |
No description provided.