Blog

Waves Enterprise releases network update

Thanks to the update, the platform’s reliability, speed and throughput will improve, and it will become easier to use.

The latest network update from Waves Enterprise offers a number of new features and benefits.

One of the most useful additions is the new address management functionality. A user who has several addresses will now be able to name them in their profile, enabling them to manage the different addresses conveniently. Only the user will be able to see the names of their addresses.

The new release will also see an improved process for importing accounts. A wizard will take the user through the import procedure step-by-step, making importing addresses much easier and more user-friendly than before.

The update also provides functionality for using an API Key for private keys on your node. Previously, only use of nodes on which authorization was turned on was supported.

Version 1.1.0 also sees an upgraded protocol for connecting new nodes. A TCP connection is now sufficient for connecting a new node. This improvement simplifies the deployment of nodes in closed systems where opening a new port (especially an http port) requires additional approval, for example by the security department.

The Docker client for smart contract operation was replaced. Instead of a solution from Spotify, a native Java client is now used, which has broader functionality and enables a greater level of security and higher speeds.

In the updated version, the node can interact simultaneously with several Network Time Protocol (NTP) servers, which improves the system’s fail safety. NTP servers are vital for the Proof of Authority (PoA) consensus algorithm. Previously, the unavailability of an NTP server could lead to problems in the consensus operation.

Mainnet configuration settings are now embedded in the node. While deploying a node on mainnet, users no longer have to set the entire configuration: all relevant parameters have already been added.

In addition, the operation speed of Docker contracts has been optimized. Now, only data for updated keys is added to a transaction with the results of contract operation. This reduces data duplication on the blockchain and improves productivity, as more data can be put into each transaction.

In the new release, the node restart mechanism was improved. As a result, working with blockchains deployed in a container orchestrator infrastructure has become easier since container restart is often required in infrastructures of that kind, and the ability to do this in a stable and fast manner is vital.

A check for system resource sufficiency at node launch was added. The minimum requirements are a dual-core processor, 2 GB RАМ and 50 GB HDD. At the node configuration stage, this check can be disabled, but we strongly recommend that users do not do so. A successful launch with insufficient resources cannot guarantee the node’s stable operation at full capacity.

The crypto provider used for GOST cryptography node operation was replaced. Instead of CryptoPro JCP, we now use CryptoPro CSP. This is a native crypto provider that runs much more quickly, resulting in a 350% increase in the speed of cryptographic operations. In addition, this crypto provider is certified under the KS-2 protection class, which in turn allows systems developed on our platform to be certified under a higher protection class.

Finally, in the new version, descriptions of errors sent by the node were improved.

Also, we’d like to inform users in advance that in the next release, the node will switch to a licensing model. In order to launch a node, the user will need a license — either commercial or non-commercial. Users will be able to acquire licenses in their personal profile via the support service, which will also be introduced in the coming release.