Fixes for clusterid and sharding, use autosharding in testnet

[NagyZoltanPeter]

Changes for logos-core headless mode messaging node config

• Updated clusterId, set 2 as opinionated testnet clusterId
• numShardsInNetwork represent autosharding in use, that is proposed for testnet v0.1
• Removed "relayTopic" as it is not used, I guess it was a leftover from go-waku.

Further proposal

As this config seems to be a status fleet config we will need to update with new fleet data.
As a follow up I propose for the testnet v0.1

• clusterId = 2 for logos testnet
• use autosharding as default, hence: --numShardsInNetwork = 8
• Update enrtree url with new testnet fleet one.
• logos-core message delivery nodes shall support discv5 and peerExchange.
• debatable but I would add lightpush and filter also enabled to support edge mode clients.

[jakubgs]

I don't even know what this is for.

[NagyZoltanPeter]

I don't even know what this is for.

I included you to get notified about the discussion around new logos.dev/logos.test planned configuration.
This file is meant for input for running Logos.node (former Logos Core headless mode node) for messaging fleet.

IDK if you already got any demand on how its gonna look like in setup.

[chaitanyaprem]

@NagyZoltanPeter i would like atleast this version to be deployed or anything after the PR is merged.
This is required for mix and cap-disc to work and demonstrated.

Additional config that would be required

enable-kad-discovery=true
kad-bootstrap-node=  , not required for node1 and rest of the nodes can use node1 multiaddr (including peerId)
mix = true
lightpush=true

Should i raise a separete PR or will you update yours itself?

[igor-sirotin]

@NagyZoltanPeter perhaps makes sense to wait for status-im/infra-logos#1

[NagyZoltanPeter]

includi

Hey Prem!
I think I need something to clarify.
As these config will be a base of Logos.dev (testnet v0.1) node's configs, are these kad-disco and mix will help those nodes to become mixifying nodes in the network (the nodes that will form the mix network)?
In other words are we enabling mix on all the nodes to enable forming random mixify network of them?

If so, I see no issue with that, with the note it will be avail for clients using KernepAPI lightpushPublish for now.

[NagyZoltanPeter]

@NagyZoltanPeter perhaps makes sense to wait for status-im/infra-logos#1

Exactly as we need inputs from them at least bootstrap nodes addresses to configure it here.

[chaitanyaprem]

As these config will be a base of Logos.dev (testnet v0.1) node's configs, are these kad-disco and mix will help those nodes to become mixifying nodes in the network (the nodes that will form the mix network)?
In other words are we enabling mix on all the nodes to enable forming random mixify network of them?

Yes, you are right.

with the note it will be avail for clients using KernepAPI lightpushPublish for now

that is fine, because the APi to publish will onyl be used by nodes that want to publish messages into the network and fleet nodes would not be publishing messages rather just relaying them. So the logos-chat-app will use the PR which includes kernetAPI which is one of the reasons i have split the changes as well :)

[chaitanyaprem]

• debatable but I would add lightpush and filter also enabled to support edge mode clients.

We should add support for lightpush and filter as well. Mix publishing will not work if lightpush is not enabled.