Skip to content

Version 0.5.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@alexeykiselev alexeykiselev released this 03 Apr 12:59
· 1078 commits to master since this release
v0.5.0
This tag was signed with the committer’s verified signature.
alexeykiselev Alexey Kiselev
GPG key ID: 9C7E78FA7CED3A90
Learn about vigilant mode.
50989c6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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!

Assets 14
Loading