chore(js-waku)!: update API for NetworkConfig #193
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| const shardInfo = { clusterId: 3, shard: 1 }; | ||
|
|
||
| // Create Filter subscription with custom shard info | ||
| const subscription = await node.filter.createSubscription(shardInfo); |
There was a problem hiding this comment.
just a heads up that it will change soon as the current API seems to be too hard to understand. Maybe we can delay this PR or we can follow up on it. I think we will have it updated in a week or so
| @@ -24,6 +24,19 @@ await node.start(); | |||
| When the `defaultBootstrap` parameter is set to `true`, your node will be bootstrapped using the [default bootstrap method](/guides/js-waku/configure-discovery#default-bootstrap-method). Have a look at the [Bootstrap Nodes and Discover Peers](/guides/js-waku/configure-discovery) guide to learn more methods to bootstrap nodes. | |||
| ::: | |||
|
|
|||
| A node needs to know how to route messages. In order to do that you can use standard pubsub topic (`/waku/2/default-waku/proto`). If your project uses a different shared pubsub topic, you can configure this using the `ShardInfo` parameter or by using a set of `contentTopics` that your node will be using: | |||
There was a problem hiding this comment.
nothing to be done right now: heads up that we will soon change the default pubusb topic to the The Waku Network, pending RLN as a Service for Light Clients is merged on nwaku side
There was a problem hiding this comment.
update: nwaku has merged this feature and will be released this week. js-waku will followup
cc @weboko
There was a problem hiding this comment.
What's the new pubusb topic?
There was a problem hiding this comment.
It's going to be The Waku Network by default -- we are yet to start a PR for it though.
LordGhostX
force-pushed
the
shard-info-js-waku
branch
from
7f4ac16 to
5af7525
Compare
|
@waku-org/js-waku can we merge this? |
The API is updated again from the time this PR was opened -- the new API are here: https://github.com/waku-org/docs.waku.org/pull/213/files Will open a PR against this branch to update the docs here |
|
Opened a PR here: #221 |
|
@danisharora099 should the present PR be closed then? |
danisharora099
force-pushed
the
shard-info-js-waku
branch
3 times, most recently
from
1328218 to
91292db
Compare
danisharora099
force-pushed
the
shard-info-js-waku
branch
from
91292db to
430e395
Compare
Merged that PR here, looks good to merge now |
danisharora099
force-pushed
the
shard-info-js-waku
branch
from
430e395 to
428e184
Compare
Co-authored-by: Sasha <[email protected]>
danisharora099
force-pushed
the
shard-info-js-waku
branch
from
428e184 to
e34e764
Compare
danisharora099
changed the title
danisharora099
force-pushed
the
shard-info-js-waku
branch
from
0ea348e to
d99cab3
Compare
danisharora099
force-pushed
the
shard-info-js-waku
branch
from
d99cab3 to
350dacc
Compare
Resolves issue #131
Preview: https://docs-waku-org-git-shard-info-js-waku-acidinfo.vercel.app/guides/js-waku/light-send-receive