After a week of testing Hosted Elemental Chat with over 120 HoloPorts, we had 50+ pre-release testers and nearly 400 messages. Then, we encountered an issue that has had us briefly pause the testing. The chat entries were working quite well but the blocking issue was with the Service Logger.
Service Logger is the Holochain application that runs on each and every HoloPort and is connected to the Holo Hosting hApp. It logs hosting in the form of storage, bandwidth and CPU usage and it provides proof of work records for hosts to be able to send valid invoices to publishers. Without sharding built into Holochain, our standard configuration for Service Logger is overwhelming the network with gossip entries for these logs. We’re going to make some changes to the configuration so as to log much less frequently for now, and then we’ll bump it back to the normal settings after we have tested sharding successfully on the Holo network.
We are making a few other changes for this test as well. One is a simple change to the link we send testers for creating their credentials - we’ll specify the signup form instead of the login form, so people start in the right place.
Another fix we completed that we are now testing is related to the registration codes that people are required to use to join the test. Many people were receiving false positive error messages that indicated their registration code had been used previously, when it had not. We’ve changed how the process works and are testing to ensure the incorrect error messages no longer appear.
After another day or so of dev testing for these changes, we’ll proceed with our Pre-Release test of Hosted Elemental Chat.
On a related note, the Holochain team is making good progress with the sharding feature.