• Status chat protocol benchmarks report: Status-backend chat protocol benchmarks
• Discord thread with the main discussion: https://discord.com/channels/1110799176264056863/1414975481438011392

After a lot of research (special thanks to Igor, Patryk, Richard, and the rest of the persons that participated in the discussions), there was basically a problem with discovery.

During the benchmarks, the main issue of the scalability of the scenarios was that Status nodes were not able to find each other. This was causing a huge bottleneck in the nWaku bootstrap node and store node, that was the central point where every Status node (full and light) was connected and was sending/receiving messages through it.

The events were more or less the following ones:

There were not (? or was not working) a functional test in status that checked node discoverability. This was done and fixed a bug where the containers were getting multiple docker networks, and because of this they were not able to discover each other:

https://github.com/status-im/status-go/issues/6886

https://github.com/status-im/status-go/pull/6901

Then, there was the issue that we would need to set up an ENRtree just for those tests, so the following PR was done:

https://github.com/status-im/status-go/pull/6941

There was still an issue in the following situation:

1. I have a nwaku bootnode running.,
2. Then I start a status-backend. ,
   • The container gets some IP 172.20.0.6.,
   • The go-waku instance selects a random port 22333,
   • We use an ephemeral private key for waku, so it has a random PeerID,
   • Let's call the above ENR-1,
3. Here status-backend: ,
   • statically connects to the bootnode, ✅
   • can be discovered through peer exchange, ✅
4. Now, keeping the bootnode running, I restart the status-backend,
   • it gets the same IP 172.20.0.6,
   • it selects a random port 33444,
   • new ephemeral private key, so a new PeerID,
   • Let's call the above ENR-2,