status-im
/
js-waku
mirror of https://github.com/status-im/js-waku.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
13 Commits 70 Branches 297 Tags 205 MiB
Commit Graph

13 Commits

Author SHA1 Message Date
Franck Royer b8c63355a5
Ensure waku relay node does not use a sub protocol 
At the moment we do not assert that we publish messages over waku relay
protocol (not sure this assertion is possible).
By asserting we do not register any sub (pubsub, gossipsub, floodsub)
protocols, we can be (more) confident that this
protocols are not be used behind the scenes.
 2021-03-10 16:25:54 +11:00
Franck Royer 4329b8006e
Use waku messages over waku relay 2021-03-10 16:22:49 +11:00
Franck Royer 070847d2c0
Use waku relay interface to subscribe and publish messages 2021-03-10 15:15:36 +11:00
Franck Royer 12c2a93c7f
Register waku protocol instead of gossip sub 2021-03-10 15:08:27 +11:00
Franck Royer 525815528f
Remove message signing as per waku specs 2021-03-10 14:58:04 +11:00
Franck Royer b5bf5c03ab
Reduce test verbosity 2021-03-10 14:56:12 +11:00
Franck Royer dfe08058d9
Use promises to remove one delay 2021-03-10 14:55:16 +11:00
Franck Royer 8e91ca6d01
Adopt more typescript-y syntax, do not lint generated files 2021-03-10 14:30:31 +11:00
Franck Royer 5e64708111
Can use gossipsub to publish messages 2021-03-10 14:24:23 +11:00
Franck Royer be47223bae
Connects to nim-waku using waku-relay protocol 2021-03-05 14:41:20 +11:00
Franck Royer 512115ae8c
Run audit fix 2021-03-05 09:48:39 +11:00
Franck Royer 2e5823cfe3
Fix tests 2021-03-05 09:41:03 +11:00
Franck Royer f46ce77f57
Initial commit 
Created with bitjson/typescript-starter@586cdb3029
 2021-03-05 09:34:01 +11:00