CLI Command Reference
Open the command line, navigate to the directory where NEO-CLI is located, and enter the following code to start the command line wallet (ie the NEO node).
This tutorial will introduce all the commands in the command line wallet. You can manipulate your wallet with commands for creating a wallet, importing and exporting of private key, transferring, starting consensus, etc.
We will first explore the various commands listed in the command line. In the command line, enter
help followed by a return command, and you will see a list of commands as shown.
The following is a description of all the commands and the order of the brackets:
<> indicate a parameter.
 is for optional parameters.
The pipe symbol
| separates multiple parameters where any one of them can be used at your choice.
The equal sign
= indicates the default value of the optional parameter without an input.
|version||Shows the current software version|
|create wallet <path>||Create wallet file|
|open wallet <path>||Open wallet file|
|rebuild wallet index||Need to open wallet|
|list address||list all the accounts in the wallet||Need to open wallet|
|list asset||List all assets in the wallet||Need to open wallet|
|list key||List all public keys in your wallet||Need to open wallet|
|create address [n = 1]||Create address / batch create address||Need to open wallet|
|import key <wif|path>||Import private key / bulk import of private keys||Need to open wallet|
|export key [address] [path]||Export private key||Need to open wallet|
|send <id|alias> <address> <value> [fee=0]||Send to the specified address||Need to open wallet|
|import multisigaddress m pubkeys...||Create a multi-signature contract||Need to open wallet|
||Sign the transaction. The parameter is the json string that records the transaction information||Need to open wallet|
||Broadcast the transaction. The parameter is the json string that records the transaction information||Need to open wallet|
The following commands are explained in detail:
This command is used to rebuild the wallet index. Why is it necessary to rebuild the wallet index?
There is a field in the wallet that records the height of the current wallet sync block. For each new one, the wallet client synchronizes the blocks and updates the assets, and transactions in the wallet. Assuming that the current, recorded block height is 100, then you execute the import key command to import the private key, the wallet still calculates your asset from the block height of 100. If the imported address has some transactions when the block height is less than 100, the transactions and the corresponding assets will not be reflected in the wallet, so the wallet index should be rebuilt, forcing the wallet to calculate your assets from the block height of 0.
The newly created wallet does not need to rebuild the wallet index, only the imported private key is required to rebuild the wallet index.
create address [n = 1]
This command can be used to create a new address. One can also enter 'create address 100' to create 100 new addresses in batches; Batch creation of the address will be automatically exported to the address.txt file.
export key [address] [path]
You can specify which addresses to export the corresponding private keys to. You can also specify the export to the specified file. (See below for examples). The command also requires the verification of the wallet password.
Export key AeSHyuirtXbfZbFik6SiBW2BEj7GK3N62b
Export key key.txt
Export key AeSHyuirtXbfZbFik6SiBW2BEj7GK3N62b key.txt
import key <wif | path>
When importing the private key, you can specify to import a private key, or import a file with a number of private keys. (The following commands are legal)
Import key L4zRFphDJpLzXZzYrYKvUoz1LkhZprS5pTYywFqTJT2EcmWPPpPH
Import key key.txt
If there is a specified file, the file is in the private key format. Refer to export key key.txt output.
send <id | alias> <address> <value> [fee = 0]
For transfers, there are a total of four parameters. The first parameter is the asset ID, the second parameter is the payment address, the third parameter is the transfer amount, and the fourth parameter is the fee. (This parameter can be left empty, and the default is 0) The command needs to verify the wallet password. For example, in order to transfer 100 NEO to the address "AeSHyuirtXbfZbFik6SiBW2BEj7GK3N62b", one would need to enter the following command.
Send c56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b AeSHyuirtXbfZbFik6SiBW2BEj7GK3N62b 100
If you are not sure of the asset ID, please enter the list asset command to view all assets in the wallet.
import multisigaddress m pubkeys...
The command is used to create a multi-party signed address. m is the minimal number of signatures. For example, creating a multi-party signed address with two public keys, m can be 1 or 2, and the parameter followed are the two parties public keys.
This command is used to sign when withdrawing assets from a multi-signed address which requires multiple signatures. The parameter is the json string that records the transaction information. The translation can be broadcasted only after signing is completed.
After signing completed, this command can be used to broadcast the transaction information. The parameter is the json string that records the transaction information.
View the node information
|show state||Displays the current status of blockchain synchronization|
|show node||Displays the address and port of connected nodes|
|show pool||Display the transactions in the memory pool (These transactions are in the state of zero confirmation)|
|export blocks [path=chain.acc]||Exports the whole blockchain data. The exported data can be used for offline synchronzation.|
||Exports a specified number of block data from the specified block height. The exported data can be used for offline synchronization.|
|Start consensus||Begin consensus|
Start the consensus on the premise that the wallet has a consensus authority, allows consensus authority to be obtained on the main net through voting. If a private chain is deployed, public key of the consensus can be set up in the
protocol.json. Please refer to Private chain for further details.