In parallel to the back-end development, we’re now also starting to experiment with the front-end, i.e. the part of the system that directly interacts with the users. And while it is largely work in progress, we’ve decided to share the current state on our official website so that you might follow its evolution as we add and refine details:

It is worth noting that there are going to be two separate interfaces in Nexusless: one for the content originators and another for the participants of the network who earn money as edge nodes delivering the content. The current reveal only concerns the edge node client, which is expected to be much more widely used compared with the originator client.

The edge node client will be installable on personal computers (Windows, Mac) and mobile devices (iOS and Android); it primary purpose is to serve as a dashboard and personal wallet. The left section of the application is a menu (on mobile devices it is triggered by clicking on the hamburger icon next to the logo) containing links to the various sections.

We will post new information and explanations as the prototype gets updated, here are some comments on the “Resource Settings” section:

Since content storage and delivery requires computing and network resources, it is of outmost importance to ensure that every edge node user is able to adjust the resource consumption of their node, corresponding with their personal preferences. The Resource Settings section allows manually setting specific limits for each of the resources consumed by an active edge node, such as bandwidth, storage, memory, or battery usage (for mobile devices and laptops).

The data traffic cap is especially important for metered connections such as mobile data plans, and will directly affect the edge node earnings, thus the prominent position of this setting. It is defined in Megabytes per day and can be adjusted in the multiples of ten – the user can click on the plus and minus buttons to set the desired value.

Battery use, RAM allocation and storage limits can also be set in this section in order to provide more granular control over the parameters of the edge node. Note that each setting has a default value that has been set to ensure reasonable resource consumption by non-customized default node. The battery and memory limits are set in percentage points and both have a maximum value of 50% to protect the device from excess strain.

For an in-depth discussion of the resource consumption issue and its implications, please see the part 4.3 of our technical whitepaper.

We are happy to receive comments, feedback, and critique on the prototype, your wishes and feature requests will be added to our backlog.

More details about the edge node client as well as reveal the content originator client are planned for the upcoming weeks, stay tuned via our Telegram group, Facebook page or Twitter feed!

Leave a Reply