status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-go/config/cli/fleet-wakuv2.prod.json

25 lines
747 B
JSON
Raw Normal View History

go-waku integration (#2247) * Adding wakunode module * Adding wakuv2 fleet files * Add waku fleets to update-fleet-config script * Adding config items for waku v2 * Conditionally start waku v2 node depending on config * Adapting common code to use go-waku * Setting log level to info * update dependencies * update fleet config to use WakuNodes instead of BootNodes * send and receive messages * use hash returned when publishing a message * add waku store protocol * trigger signal after receiving store messages * exclude linting rule SA1019 to check deprecated packages
2021-06-16 20:19:45 +00:00
{
"Rendezvous": false,
"NoDiscovery": true,
"ClusterConfig": {
"Enabled": true,
"Fleet": "wakuv2.prod",
"BootNodes": [],
"TrustedMailServers": [],
"PushNotificationsServers": [],
"StaticNodes": [],
"RendezvousNodes": [],
"WakuNodes": [
config/cli/fleet: disable Rendezvous, drop nodes Since we've broken LibP2P communication with our Rendezvous nodes somewhere after `v0.79.11` we should not enable it by defaults since it generates errors like these: ``` failed to dial 16Uiu2...d687e4: all dials failed failed to negotiate security protocol: protocol not supported ``` Since normal bootnodes are defined as well as a list of static nodes there should not be a need for using Rendezvous as well. Resolves: https://github.com/status-im/status-go/issues/2309 Signed-off-by: Jakub Sokołowski <jakub@status.im>
2021-08-13 13:58:50 +00:00
"/ip4/8.210.222.231/tcp/30303/p2p/16Uiu2HAm4v86W3bmT1BiH6oSPzcsSr24iDQpSN5Qa992BCjjwgrD",
go-waku integration (#2247) * Adding wakunode module * Adding wakuv2 fleet files * Add waku fleets to update-fleet-config script * Adding config items for waku v2 * Conditionally start waku v2 node depending on config * Adapting common code to use go-waku * Setting log level to info * update dependencies * update fleet config to use WakuNodes instead of BootNodes * send and receive messages * use hash returned when publishing a message * add waku store protocol * trigger signal after receiving store messages * exclude linting rule SA1019 to check deprecated packages
2021-06-16 20:19:45 +00:00
"/ip4/188.166.135.145/tcp/30303/p2p/16Uiu2HAmL5okWopX7NqZWBUKVqW8iUxCEmd5GMHLVPwCgzYzQv3e",
"/ip4/34.121.100.108/tcp/30303/p2p/16Uiu2HAmVkKntsECaYfefR1V2yCR79CegLATuTPE6B9TxgxBiiiA"
],
"WakuStoreNodes": [
"/ip4/134.209.113.86/tcp/9000/p2p/16Uiu2HAmVVi6Q4j7MAKVibquW8aA27UNrA4Q8Wkz9EetGViu8ZF1"
]
},
"WakuV2Config": {
config/cli/fleet: disable Rendezvous, drop nodes Since we've broken LibP2P communication with our Rendezvous nodes somewhere after `v0.79.11` we should not enable it by defaults since it generates errors like these: ``` failed to dial 16Uiu2...d687e4: all dials failed failed to negotiate security protocol: protocol not supported ``` Since normal bootnodes are defined as well as a list of static nodes there should not be a need for using Rendezvous as well. Resolves: https://github.com/status-im/status-go/issues/2309 Signed-off-by: Jakub Sokołowski <jakub@status.im>
2021-08-13 13:58:50 +00:00
"Enabled": true
}
go-waku integration (#2247) * Adding wakunode module * Adding wakuv2 fleet files * Add waku fleets to update-fleet-config script * Adding config items for waku v2 * Conditionally start waku v2 node depending on config * Adapting common code to use go-waku * Setting log level to info * update dependencies * update fleet config to use WakuNodes instead of BootNodes * send and receive messages * use hash returned when publishing a message * add waku store protocol * trigger signal after receiving store messages * exclude linting rule SA1019 to check deprecated packages
2021-06-16 20:19:45 +00:00
}