[User Story] Incentivized network IDs

[Eknir]

Incentivized network IDs

"As a user of Swarm, I can connect to different BZZ Network IDs, such that I connect to Swarm with a different blockchain"

Epic link

Stable SWAP

Rationale

Currently, Swap may only be enabled on when BZZ Network ID == 5. This works OK, when we assume that all nodes run on the same Ethereum network ID. Obviously, this is not the case, causing nodes on the same BZZ Network ID to be not connected with each other. This convolutes the log (Error cannot connect), but it also makes the idea of one BZZ Network, as a set of nodes which are all connected, erroneous. Furthermore, if we clearly document which BZZ Network idea maps to which EVM Network ID, the user needs one less input parameter when starting Swarm.

Acceptance criteria

• A user boots up Swarm with BZZ Network ID 103, and it connects to EVM Network ID 3 (exact mapping may be different) && BZZ Network ID 104 => EVM Network ID 4

Work estimate

t.b.d.

[Eknir]

Spoken about during the research office hour on 13/2. @janos does not really like the idea of adding more semantic meaning to a BZZ Network ID and explains that in BEE, there must be a new design about "Swarm Networks" and how to identify them anyways. The issue is that even if we say that if BZZ Network ID 103 equals Blockchain network ID 3, everybody can just run Swarm, connect to BZZ Network ID 103 and run with a blockchain network ID != 3. Is the BZZ Network ID actually something that is meaningful?

The conclusion was made that, for the time being, we can pursue the proposed solution (see Acceptance criteria).