Initial Node registration

You will need to use the Gui Wallet for this step and have 1000 Stream to pay for the network fee (if you are holding multiple nodes in one address only pay the fee once):

  1. Under Advanced select GTNode and request registration

After registering we recommend using the node on the CLI Wallet with a secured environment.

IMPORTANT

If you transfer the Node to a new address, you will need to repeat the initial registration . 

To run the node it is required to have 50.000 Kaze. After the public sale has taken place nodes will not require a collateral to run and receive fees.

Installing the environment

Install one of the following depending on your system:

For Windows 7 and Windows 10,install .NET Core and .NET Framework. For Linux install .NET Core Runtime.

After the installation is complete, you can run the following command to check whether the .NET Core environment was installed successfully.

dotnet new console -o hwapp
cd hwapp
dotnet restore
dotnet run

If you see the final output "Hello World!", The .Net Core installation is successful.

Installing the Kaze-CLI package

  1. Download the latest Kaze Cli package
  2. On MacOS, install Homebrow and run the following:
brew install leveldb
brew install sqlite

On Linux, install the LevelDB and SQLite3 dev packages. For example, on ubuntu 17.10 run the following:

sudo apt-get install libleveldb-dev sqlite3 libsqlite3-dev libunwind8-dev

On Windows, you can skip this step, as those files are already included in the installation package.

Starting the Kaze node

Open the command line, navigate to the Kaze-cli directory, and enter the following command to start the KAZE node:

dotnet Kaze-cli.dll

For Developers
Kaze-CLI provides a series of APIs for external access. If you want to start the node while opening the API, you can add the parameter --rpc, /rpc, or -r, for example:

dotnet Kaze-cli.dll --rpc

Recommended
 to log the smart contract information, e.g. the NEP-6 assets transactions, you can add --log or -l, for example:

dotnet Kaze-cli.dll --log 

If you want to only connect seed nodes in the configuration file, enter the following:

dotnet Kaze-cli.dll --nopeers 

If you want an external program to access the node API, open the following firewall port:  

                   Main Net   Test Net
JSON-RPC HTTPS      22885      44885
JSON-RPC HTTP       22886      44886
P2P                 22887      44887
websocket           22888      44888

IMPORTANT

If you open the API service and the wallet in Kaze-CLI, you need to set up your firewall policy. For example, set a whitelist for the firewall to only allow access to these ports by whitelisted IP addresses. If completely opening the service to external network, others may be able to transfer assets using API.

Synchronizing blockchain data

The client must be fully synchronized before use.

Comparison of GUI node and CLI node functions

                                                          GUI              CLI

Graphic Interface                              ✅  

Command LineInterface                                      ✅ 

Create Wallet                                    ✅              ✅ 

Open Wallet                                      ✅              ✅ 

Reconstruct Wallet Index                 ✅              ✅ 

Show all keypairs                             ✅              ✅ 

Import/Export KeyPair                      ✅              ✅ 

Show all addresses                          ✅              ✅ 

Show all assets                                ✅               ✅ 

Create Address                                ✅               ✅ 

Transfer                                             ✅               ✅ 

Transaction(Asset swap)                  ✅  

Create a multi-party
signature contract                            ✅  

Create a custom smart contract     ✅  

Signature                                          ✅  

Election Consensus Node               ✅  

Voting                                                ✅  

Register assets                                 ✅  

Distribution ofassets                        ✅  

Extraction of KAZE                           ✅  

Batch GenerationAddress                                 ✅ 

JSON-RPC                                                           ✅ 

The consensus of the
participating blocks                                            ✅ 

Did this answer your question?