Version 0.8.6

In this release

This is a bug fix release. The following issues were fixed.

• Complexity of the RIDE function transferTransactionById reduced to correct value.
• Default list of seed peers on StageNet updated.

This update is mandatory on MainNet, please, update ASAP!

Version 0.8.5

In this release

• Fixed an issue with AssetInfo RIDE function for the 4th version of standard library
• Fixed an issue with gRPC API function waves.node.grpc.AssetsApi/GetInfo then it failed to return assets issued by DApps

This update is mandatory for nodes on MainNet and TestNet networks.

Version 0.8.4

Bug fix release

The incorrect RIDE type for empty payments field was introduced in previous release and fixed with this one.

Please, update your MainNet nodes ASAP.

Version 0.8.3

In the release

Few more bugs were fixed.

• Incorrect transformation of InvokeScript transaction attached payments into RIDE object fixed.
• Failure to transform a Recipient to string using RIDE function toString fixed.
• Reissue and Burn script actions with zero quantity is no longer consider invalid.

ATTENTION! This update is mandatory for nodes running on the MainNet or StageNet.

Version 0.8.2

In this release

This is a bug fix release. The following issues were fixed.

ATTENTION! This update is mandatory for nodes running on MainNet.

• Critical bug of contract evaluation regarding user functions scopes was fixed.
• Parameter handling of gRPC API method waves.node.grpc.AccountsApi/GetBalances were loosened to rise compatibility with Scala Waves Node.
• Workarounds for RIDE issued assets were introduced to Waves Market Data (WMD).

And with this release, we introduce DEB packages for the installation of Gowaves Node and Waves Market Data. Please give it a try, and feel free to report any issues.

Version 0.8.1

In the release

• Network synchronisation issues were fixed
• Debian packages that install WMD and node for MainNet and TestNet were added
• Instructions on starting node for block generation were added to README.md file

Version 0.8.0

Waves Protocol 1.2

Support of Waves Protocol version 1.2. Including VRFs, Block version 5, Protobuf transactions, Fallible transactions, RIDE v4 standard library.

• Fully reimplemented RIDE evaluator. It runs faster. Blockchain import time reduced by 30%.
• Full support of RIDE v4 standard library including Groth16 verify function on two curves.
• Full support of RIDE scripts estimation. All three versions of estimators were implemented.
• Update Asset Info transaction.
• Delete Data Entry support in Data Transaction and RIDE v4 script actions.

Version 0.7.0

In this release

Full support of version 1.2.5 of Waves Protocol.

• Additions to RIDE:
  • ecrecover function to restore a public key from a ECDSA signature
  • indexOf and lastIndexOf functions
  • New SponsorFee script action
• Reduced fee for Sponsorship transactions
• Fixed importer utility

Notes

The state is incompatible with older versions, please, rebuild it from scratch.

Your issue reports and proposals are very welcome!

Version 0.6.0

In the release

In this release we support version 1.2.4 of Waves Protocol.

In addition to functionality of the previous release we've added the acceptance of Invoke and Exchange transaction even with a failed scripts. It is possible to assess new features on StageNet now. More information on failed transactions and how you can try it on StageNet can be found at this documentation page.

What's done

• Invoke and Exchange transactions are saved on the blockchain and a fee is charged for them even if the script failed, provided that the sender's signature or account script verification passed.

Notes

The state is incompatible with older versions, please, rebuild it from scratch.

Your issue reports and proposals are very welcome!

Version 0.5.0

In the release

With this release, we support Waves version 1.2 that is in testing on StageNet now.
This release is aimed at StageNet but can be used for testing on TestNet and MainNet.

What's done

• Full blockchain support of Waves version 1.2
• Support of RIDE version 4 (except for the script estimation)
• Detachable wallet and mining
• Full gRPC API and switchable Extended gRPC API

Notes

The state is incompatible with older versions, please, rebuild it from scratch.

How to run a node on StageNet

Run the node as follows:

1. Download the suitable node's binary file from the Releases page.
2. Run the following command (pass the path to the node's state directory if necessary):

./node -blockchain-type stagenet -state-path [path to node state directory] -peers 88.99.185.128:6862,95.216.205.3:6862,49.12.15.166:6862,88.198.179.16:6862 -api-address 127.0.0.1:8083

Starting the mining node

To start the node in mining mode pass the path to the wallet file and provide the following command line parameter with the wallet's password. In this case the wallet will be unlocked at once.
If no password is given on start, the node owner can unlock the wallet later using REST API.

./node -blockchain-type stagenet -state-path [path to node state directory] \
 -peers 88.99.185.128:6862,95.216.205.3:6862,49.12.15.166:6862,88.198.179.16:6862 -api-address 127.0.0.1:8083 \
 -wallet-path [path to wallet file] -wallet-password [password]

To create the wallet file use wallet utility. See the following example:

./wallet add -w [path to wallet file]

You will be asked to provide wallet's password and seed phrase.

To unlock the wallet using API, execute the POST request to /wallet/load end-point. The post request should contain the {"password": "[password]"} JSON value and the X-API-Key header with API key value.

Building and serving Extended API

The Extended API provides access to additional information that is not required for blocks validation, such as retrieving transactions by sender or receiver addresses. This information has to be collected in the state from the beginning of blockchain, so the node should operate in Extended API mode from the very beginning and henceforth.

To start the collection of additional data run the node with -build-extended-api flag, that is set to off by default.
The additional gRPC end-points will start on gRPC API address (-grpc-address flag, that is set to 127.0.0.1:7475 by default).

Known issues

• Uneven script estimation of scripts version 3. Overestimated scripts lead to warning.
• No estimation of version 4 scripts. For now, version 4 scripts are estimated as version 2.
• Unstable transition from downloading blocks to accepting micro blocks. This can stop the node in some cases.

Your issue reports and proposals are very welcome!