DeNet team is on the line!

Informing you that we are testing DeNet.Storage now. But there is a public version available too. We’ve updated Master and Slave nodes and refined technical part of documentation.

It worth spreading that we’ve established cooperation with Daplie, which allows DeNet to broaden its geography and stability of nodes. Such events will be announced in the media center.

Here are updates from our back-office:

Updated White Paper

Updated TokenSale

Managed the first stage of partnership with Daplie

Added Media Center

Updated development Road Map

Console interface

Disabled remote access to the slave node app

File encryption

Basic file replication over slave nodes

Check for a file on the slave nodes

Say ‘cheese’ and get back to work

Console interface

To make our application available to as many people as possible, we have made a graphical and console interface. Detailed description of the console application you can read in the updated version of the technical WP, which we are preparing now.

Encryption

We understand that encryption should be performed on the client side, however, for now there is no encryption on the client site, we have added it on the master node. It works simple with using AES encryption, where the key is (pub_key / filename). This is a temporary measure, later we will also update the encryption.

File replication and verification

At the moment the file redundancy is 4x of the initial file size.

We’ve developed a checker to verify files. We need this in order to understand how the nodes behave, how reliable the verification algorithm is and to impose a rating system on it, after which we will be able to make a formula and consider the necessary redundancy of files in the network.

Why do we need this?

Now we are testing and improving the DeNet network, so many functions will be updated. To build a decentralized network, we need to know the topology of our future network, as well as the behavior of network participants.

Check our previous achievements here:

Dev week III & Dev week II & Dev week I