Start keosd and nodeos
Step 1: Boot Node and Wallet
Step 1.1: Start keosd
First let us start keosd:
keosd &You should see some output in the console that looks like this:
info 2023-03-23T21:08:18.642 keosd wallet_plugin.cpp:38 plugin_initialize ] initializing wallet plugin
info 2023-03-23T21:08:18.642 keosd wallet_api_plugin.cpp:84 plugin_startup ] starting wallet_api_plugin
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/create
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/create_key
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/get_public_keys
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/import_key
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/list_keys
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/list_wallets
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/lock
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/lock_all
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/open
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/remove_key
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/set_timeout
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/sign_digest
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/sign_transaction
info 2023-03-23T21:08:18.642 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/wallet/unlock
info 2023-03-23T21:08:18.643 keosd http_plugin.cpp:983 add_handler ] add api url: /v1/node/get_supported_apisPress enter to continue
Troubleshooting
After entering keosd &, you may encounter this message:
This is because another instance of keosd process might be running in the background. Kill all instances by pkill keosd and rerun keosd &.
Step 1.2: Start nodeos
Set configurations to start nodeos can be read here.
First create new directory to run nodeos.
Download the latest snapshot from here. Or you can download by command below and replace the [filename] with the latest snapshot.
Create new bash file.
Paste the command below to the bash file, replace the [filename] with snapshot’s filename that downloaded and save it.
Run the command below.
These settings accomplish the following:
Run Nodeos. This command loads all the basic plugins, set the server address, enable CORS and add some contract debugging and logging.
Enable CORS with no restrictions (*) and development logging
DANGER
In the above configuration, CORS is enabled for * for development purposes only, you should never enable CORS for * on a node that is publicly accessible!
Troubleshooting
After starting nodeos, if you see an error message similar to "Database dirty flag set (likely due to unclean shutdown): replay required", try to start nodeos with --replay-blockchain. More details on troubleshooting nodeos can be found here.
Step 2: Check the installation
Step 2.1: Check that Nodeos is Producing Blocks
Run the following command
You should see some output in the console that looks like this:
Let the nodeos run until the output looks like this and blocks become synchronized.
Press ctrl + c to close the log
WARNING
If you want to stop nodeos, run command pkill nodeos .
After this, before you start nodeos, remove the line of --snapshot configuration from the bash file. Then you can rerun nodeos.
Step 2.2: Check the Wallet
Open the shell and run the cleos command to list available wallets. We will talk more about wallets in the future. For now, we need to validate the installation and see that the command line client cleos is working as intended.
You should see a response with an empty list of wallets:
From this point forward, you'll be executing commands from your local system (Linux or Mac).
Step 2.3: Check Nodeos endpoints
This will check that the RPC API is working correctly, pick one.
Check the
get_infoendpoint provided by thechain_api_pluginin your browser: http://localhost:8888/v1/chain/get_infoCheck the same thing, but in the console on your host machine
What's Next?
Create Test Accounts: Learn how to create test accounts in the VEXANIUM blockchain along with troubleshooting steps.
Last updated