waku-org
/
js-waku
mirror of https://github.com/waku-org/js-waku.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
2,781 Commits 75 Branches 306 Tags 265 MiB
Commit Graph

2781 Commits

Author SHA1 Message Date
Franck Royer 40fe76a15e
CI skeleton 
It is expected to fail at this stage.
 2021-03-15 14:42:36 +11:00
Franck Royer 90390cd67c
Update readme 2021-03-15 14:35:10 +11:00
Franck Royer a6cbdf3117
Segregate logs files in single directory 2021-03-15 13:38:36 +11:00
Franck Royer 548c50668a
test: Send message from js node to nim node 2021-03-15 13:27:50 +11:00
Franck Royer c99e02af20
Allow waiting for nim waku logs from test 2021-03-15 13:25:14 +11:00
Franck Royer b7ce121955
Replace delay by waiting on correct event 2021-03-15 11:35:30 +11:00
Franck Royer eb874a956b
Only node receiving message needs to subscribe 2021-03-15 11:23:20 +11:00
Franck Royer 4c6c54cf87
Nim node subscribes to default topic as soon as it connects to js node 2021-03-15 10:28:32 +11:00
Franck Royer fdbcbe0896
Allow multiple wakunodes to be started in parallel 2021-03-12 17:08:59 +11:00
Franck Royer a0d6784e3c
Use multiaddr lib instead of string parsing 2021-03-12 17:08:58 +11:00
Franck Royer a7c666f108
Fix WakuMessage (de)serialisation 2021-03-12 17:08:58 +11:00
Franck Royer 27c433f750
Test hex conversion functions 2021-03-12 10:44:47 +11:00
Franck Royer ee38df8757
Nim-interop: nim sends message (not working) 2021-03-12 10:35:50 +11:00
Franck Royer 8ed47b2cf7
Nim-interop: subscribe 
At this stage, we are only able to check that the
subscription works on js side: it confirms that
the nim node is considered as subscribing to the same
topic.
 2021-03-12 09:46:47 +11:00
Franck Royer f0c9c3ef50
Check peer ids on both side when connecting 2021-03-11 15:02:29 +11:00
Franck Royer 057f5f80ab
test: Nim-waku connects to JS (success) 2021-03-11 11:11:37 +11:00
Franck Royer a6c1fae5a6
test: Nim-waku connects to JS (wip) 2021-03-11 10:54:35 +11:00
Franck Royer 4f63bd5835
test: Connect to nim waku 2021-03-10 17:39:53 +11:00
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