Putting SubstratumNode v0.4.2 to the Test

gepubliceerd op by Cryptoslate | gepubliceerd op

Upon the update, Substratum enthusiasts have launched nodes around the world to test the performance of the network, and so did we.

With the release of SubstratumNode v0.4.2, the network is now capable of 'self-healing' damaged routes by intelligently accounting for offline nodes and "New routes will omit any inactive nodes." Self-healing is made possible via the network's "Gossip" technology, which automatically alerts an offline node's connected neighbor nodes so that future requests are not routed to the offline node.

According to Substratum, the previous v0.4.1 release "Required nodes to bootstrap from a single centralized entity to be in the same neighborhood." A bootstrap node is effectively a centralized database that contains information about other nodes on the Substratum network and how to connect to them.

In v0.4.2, nodes can be bootstrapped from any node on the network by gossiping, and a dedicated centralized bootstrap node is no longer needed to join the Substratum network.

In addition to launching a SubstratumNode test community which has attracted over eighty members, Substratum ambassador Bastiaan van der Bijl has taken the initiative to set up a decentralized neighborhood consisting of twenty-three nodes "Around the globe."

In a follow-up tweet, van der Bijl shared a screenshot of a "Speed test with 17 nodes through the Substratum network." The screenshot, which was retweeted by Substratum CMO Christian Pope, shows an impressive 347.14Mb/s download speed and 9 ms ping time.

By design, SubstratumNode routes traffic through one or more nodes, or hops, before reaching the destination.

After establishing a successful baseline in our first test, our second test introduced geography into the equation by routing traffic through a decentralized network of nodes in Singapore, Bangalore, Frankfurt, New York City, Toronto, and San Francisco.

Since the average ping time between San Francisco and Frankfurt is 146 ms, the high ping time we observed was likely due to SubstratumNode routing traffic through one or more additional nodes before exiting at Frankfurt.

It's important to note that SubstratumNode logs data even when traffic is not being routed through the node.

x