Migrate current clients of wakuv2 fleets to this one

[jakubgs]

Apparently according to @vpavlin the wakuv2.prod fleet:

runs the default pubsubTopic and is used as bootstrap for all js-waku apps, nwaku-compose etc...

We need to fix this in order to deprecate and decomission wakuv2.* fleets and start using this fleet.

Is this correct @jm-clius ?

[jm-clius]

This is true. The work necessary to get to this point is what's listed under waku-org/research#3 (i.e. finish the groundwork for using the new public Waku Network with sharded pubsub topic).

[vpavlin]

nwaku-compose is migrated, js-waku is also "migrated" by default, but since The Waku Network requires RLN proofs which is unsolved item for js-waku at this point, for any development on top and usage of js-waku we still need a fleet supporting default pubsubTopic - does not necessarily need to be wakuv2.prod though

[danisharora099]

Thanks @vpavlin !
js-waku currently heavily relies on the DefaultPubsubTopic by default as it currently does not support The Waku Network

[jakubgs]

@danisharora099 where exactly in js-waku are wakuv2 fleets used? And which one is it? test or prod?

[danisharora099]

@danisharora099 where exactly in js-waku are wakuv2 fleets used? And which one is it? test or prod?

We use the test fleet here: https://github.com/waku-org/js-waku/blob/e49e7289ae632a1c2f3d11b9dc668ca68749ac7c/packages/core/src/lib/predefined_bootstrap_nodes.ts#L57

[jakubgs]

@danisharora099 that's fine, you can use waku.* fleets wherever you want, I'm only interested in usage of wakuv2.prod fleet.

Currently I've decommissioned wakuv2.test and left only node-01.do-ams3.wakuv2.prod host in wakuv2.prod:

• infra-nim-waku#cc2d870c - wakuv2-test: decomission unused fleet
• infra-nim-waku#f71c4ff9 - requirements: bump nim-waku role
• infra-nim-waku#8c51855f - prod: drop 2/3 hosts, keeping only do-ams3 one

This host will also be decommissioned once js-waku developers confirm they no longer need it and use only waku.* fleets.