GRIDNET Core 1.1.0

Version: 1.1.0

Download URL:

[Release Notes]:

  • The ⋮⋮⋮ Decentralized UI is now much better aware of the quality and state of the underlying connection(s) with ⋮⋮⋮ Core Nodes.

Friends of Freedom! Friends of ⋮⋮⋮ Decentralization! Let us explain the rationale. Imagine you’ve booted into the ⋮⋮⋮ Decentralized UI. The thing about connections is that these do not last forever. Connections can break, the quality of these can degrade over time. Connections between the ⋮⋮⋮ Decentralized UI (which runs within a web-browser) and the ⋮⋮⋮ that serve these, are under-the-hood handled through our data-exchange protocol (binary, BER-encoded) atop of web-sockets.

The decentralized ⋮⋮⋮ might be served by multiple nodes. Now, up until now, we’ve had quite solid passive detection and management of connection. What does passive management mean? The ⋮⋮⋮ UI (and its underlying ⋮⋮⋮ VM Context) reacted well to events that were indicated either by the web-browser’s API or explicit ⋮⋮⋮ Datagrams.

Now we’ve largely improved active monitoring of connections with ⋮⋮⋮ Core nodes.

How? We have introduced additional keep-alive mechanics.

Every 2 seconds or so, each ⋮⋮⋮ Node with which the ⋮⋮⋮ UI Session expects to have a connection established with, it would be supposed to deliver a keep-alive datagram just to indicate that the connection is still alive.

Would the ⋮⋮⋮ UI notice that no datagram has arrived within half-the-timeout period - it would indicate degraded connection quality to the user by blinking the Connection LED (top of the UI, within the ⋮⋮⋮ LED Bar). Should a ⋮⋮⋮ Core not provide a keep-alive datagram for about 10 seconds, the connection would be terminated abruptly by the ⋮⋮⋮ VM Context (part of the ⋮⋮⋮ UI sub-system). The ⋮⋮⋮ VM Context would then attempt to establish a connection anew with one of the ⋮⋮⋮ Core Nodes discovered through the Kademlia-based, decentralized peer discovery protocol.

Operator! Feeling like taking these mechanics for a spin yourself? Simply connect to the ⋮⋮⋮ Decentralized UI (ex. and once the connection is established… disconnect your Wi-Fi. You would see all the above described mechanics kicking into action. (enable Google Developer’s Tools or extract the ⋮⋮⋮ Event Pane for additional low-level events.)

  • improvements to the Open CL sub-system.

  • now if you choose neither CPUs nor GPUs to be used ⋮⋮⋮ Core would autonomously assume that ⋮⋮⋮ Key-Blocks are not to be formed.

  • improvements to synchronization of the ⋮⋮⋮ Decentralized State Machine.
    While we haven’t spotted any serious troubles (this time), we’ve spotted one or two minor bugs. These have been fixed already.

As always, everything was implemented, validated and tested 100% on our YouTube LIVE channel with changes being described on our Twitter profile as these were being introduced and ideas conceived.

⋮⋮⋮ Operators! Winter Season is in its fullness already! Make sure to take benefit of the ⋮⋮⋮ Winter Season special offers and bonuses! These were described in quite a detail within Release Notes of version 1.0.9.