Neo (N3) Neo Legacy
Show / Hide Table of Contents

Deploying NEO Nodes on Server

Install NEO client

  1. Install .NET Core Runtime on the server, 2.0 and the later version.

  2. From GitHub, download the NEO-CLI program and enable the NEO node.

Install plugins

Since NEO-CLI 2.9.0 some additional functionalities are individually encapsulated in plug-ins for the purpose of improving node security, stability, and flexibility. For more information, refer to Installing plugins .

Go to here to download plugins. Exchanges need to install the following plugins to get the complete functionality of transaction log API and automatic synchronization with the offline package:

  • ApplicationLogs

  • ImportBlocks

  • RpcWallet

  • SimplePolicy

  • RpcSystemAssetTracker (Recommended)

  • CoreMetrics (Recommended)

  • RpcNep5Tracker(Recommended)

Copy the unzipped plugins into the NEO-CLI root directory, as shown below.

PluginsForExchange.png

For NEO-CLI 2.9.4 and later, you can install plugins using CLI commands：

install ImportBlocks
install ApplicationLogs
install RpcWallet
install SimplePolicy
install RpcSystemAssetTracker
install CoreMetrics
install RpcNep5Tracker

  • A set of wallet-related RPC API have been moved to the plugin RpcWallet since NEO-CLI 2.10.2. Ensure you have installed the plugin before you invoke these APIs.

  • You must install the ApplicationLogs plug-in before synchronizing the NEO client, otherwise the log in the blocks synchronized before will be lost.

Configuring config.json

Before running NEO-CLI, you need to configure the following parameters in the config.json file:

  • BindAddress: It defaults to local 127.0.0.1. You can set it to the ipv4 address of the specified NIC to allow RPC invoking. If no object is specified, it can be set to 0.0.0.0.

  • ExtraGasInvoke: Add extra GAS on top of the 10 Gas free system fee to let VM perform more content.

  • MaxConcurrentConnections: Maximum concurrent connections allowed for RPC invoking.

  • UnlockWallet: Optional. You can enable automatic binding and opening of the wallet. The following is an configuration example, where Path is the wallet path, Password is the wallet password, and IsActive is set to true to allow the wallet to be opened automatically.

 {
  "ApplicationConfiguration": {
    "Paths": {
      "Chain": "Chain_{0}",
      "Index": "Index_{0}"
    },
    "P2P": {
      "Port": 10333,
      "WsPort": 10334
    },
    "RPC": {
      "BindAddress": "127.0.0.1",
      "Port": 10332,
      "SslCert": "",
      "SslCertPassword": "",
      "ExtraGasInvoke": "0",
      "MaxConcurrentConnections": "10"
    },
    "UnlockWallet": {
      "Path": "",
      "Password": "",
      "StartConsensus": false,
      "IsActive": true
    },
    "PluginURL": "https://github.com/neo-project/neo-plugins/releases/download/v{1}/{0}.zip"
  }
}
...

If you want to enable automatic opening of a wallet, specify the parameter "Path" and "Password" with the corresponding wallet information, and set "IsActive" to true. But be cautious before you do that, make sure your firewall is open and safe as Password specified in the file is in clear text.

For more information, refer to Installation and deployment of NEO node .