This section provides information on the node's command-line interface.
CLI stands for Command Line Interface.
humanode-peeris a command line application, and it exposes a CLI as all the other console commands do.
humanode-peeris an executable with multiple subcommands. If no subcommands are specified, it will run as a Humanode blockchain node (we call it "run command"). If a subcommand is specified, the relevant subcommand will be executed.
To learn about the available subcommands, flags and options use the
$ humanode-peer --help
Humanode is built on top of the Substrate framework, and we reuse most of the CLI from the standard Substrate layout.
Please refer to the Substrate documentation to learn more about the standard Substrate CLI:
You would typically run your blockchain node with the following arguments.
$ humanode-peer --chain your-chainspec.json
For development, it is nice to use
$ humanode-peer --dev
We have a few flags that we've added on top of the standard Substrate CLI for the run command.
For the rest of the flags, please see the Substrate documentation as referred in the General CLI layout section.
There is a list of bioauth-related options and flags.
The URL of robonode to authenticate with. Optional, typically set in chainspec so you don't have to pass it manually.
The URL to use for the web app. Used to print the QR Code to the console. Optional, typically set in chainspec so you don't have to pass it manually.
The URL to pass to the web app to connect to the node RPC.
If not passed, a URL with
Detect RPC URL from
The tunnel name at
What RPC URL port to prefer. [default:
Explicitly unset the RPC URL. Might be useful if you want to do something exotic, but generally, you'd want the RPC URL set.