Skip to content
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

Waku 0: integrate Waku node and Waku client #1683

Open
adambabik opened this issue Nov 18, 2019 · 2 comments
Open

Waku 0: integrate Waku node and Waku client #1683

adambabik opened this issue Nov 18, 2019 · 2 comments

Comments

@adambabik
Copy link
Member

@adambabik adambabik commented Nov 18, 2019

Problem

Statusd as well as status-go libraries should have Waku node/client service instantiated when it is enabled in the configuration.

Implementation

Following the current strategy in status-go, add a WakuConfig to params.NodeConfig. If enabled, a Waku node/client service should be instantiated, similarly to Whisper service.

Waku service should be visible as a separate subprotocol.

Acceptance Criteria

  1. Status-go library can communicate with Waku node using a separate subprotocol.
  2. Statusd can run with Waku node subprotocol enabled and server Waku nodes.
  3. Statusd has an additional command which is a CLI implementation of Waku client.

Requirements

  1. Waku service is implemented first -- this will be done in a separate repo similarly to Whisper.
@oskarth

This comment has been minimized.

Copy link
Member

@oskarth oskarth commented Nov 18, 2019

Thanks - one more thing to keep in mind is that there's a need for a WakuWhisper bridge, we are currently experimenting with this in the nim-eth code base

@oskarth

This comment has been minimized.

Copy link
Member

@oskarth oskarth commented Jan 14, 2020

@adambabik is this the most up to date master issue for status-go Waku client? Does it cover:

	- shhext (https://github.com/status-im/status-go/pull/1777)
	- topic interest (_)
	- mailserver topic interest (_)
	- bridging logic (_)
  	- full spec compliant (link to issue?)
  		- simulation would be useful for this

?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.