Waves Enterprise, the custom blockchain solution for business from Waves, has announced its first new updates since a major upgrade was initiated back in November.
One of the most useful additions is a new address management functionality. A user who has several addresses will now be able to name them in their profile. This enables better management of different addresses, and only the user is able to see the names of their addresses.
The new release also sees 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 Version 1.1.0 update now provides functionality for using an API key for private keys on a node. Previously, only the use of nodes where authorization was turned on was supported.
Further, version 1.1.0 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.
Further, 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 1.1.0 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 are added to a transaction with the results of the 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 also 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 it is strongly recommended 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 the GOST cryptography node operation has also now been replaced. Instead of CryptoPro JCP, Waves Enterprise now uses 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 the Waves Enterprise platform to be certified under a higher protection class.
Finally, in the new version, descriptions of errors sent by the node were improved.
“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.”
– The Waves Enterprise Team