Humanode Docs
  • Quick Start
  • Overview
  • Concepts
    • Bioauth
    • Smart Contracts
    • Node
    • Validator
  • Chains
  • Help & Support
    • Troubleshooting
    • FAQ
    • Discord
  • Node
    • About
    • System Requirements
    • Setup
    • CLI
      • Dev Mode
    • JSON-RPC
    • Tools & Services
  • Humanode Launcher
    • About
    • Launcher Installation
    • Workspace Creation
      • Remote
      • Local
        • Linux / macOS
        • Windows
    • Node Installation
    • Node Configuration
    • Running the node
    • Stopping the node
  • Humanode Distribution
    • About
    • Preparation
    • Node Installation
      • Manual Installation
    • Running the node
  • Validators
    • About
    • Becoming a validator
    • Checking validator status
  • Tools & Services
    • Polkadot.js apps
    • Polkadot.js extension
      • Wallet Setup
    • EVM Playground
    • Subscan
    • Exchanges
    • Oracles
    • Testnet Faucets
    • Substrate API Sidecar
    • Humanode Truffle Box
    • Humanode Token Claim
  • Bioauth
    • About Bioauth
    • Enrolling
    • Authenticating
    • Robonode
  • EVM & Solidity Smart Contracts
    • EVM Compatibility
    • Precompiles
    • Architecture
    • HMND/eHMND swap
    • EVM Dev Mode & Keys
    • Sample contract: ERC20 token
    • EVM Playground
    • Humanode Truffle Box
Powered by GitBook
On this page
  • What is CLI
  • General CLI layout
  • Usage
  • Run command
  • Bioauth flags and options
  1. Node

CLI

This section provides information on the node's command-line interface.

PreviousSetupNextDev Mode

Last updated 1 month ago

What is CLI

CLI stands for Command Line Interface.

humanode-peer is a command line application, and it exposes a CLI as all the other console commands do.

General CLI layout

humanode-peer is 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 --help flag:

$ 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:

Usage

You would typically run your blockchain node with the following arguments.

$ humanode-peer --chain your-chainspec.json

For development, it is nice to use --dev flag:

$ humanode-peer --dev

Run command

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.

Bioauth flags and options

There is a list of bioauth-related options and flags.

Bioauth options
Description

--robonode-url <ROBONODE_URL>

The URL of robonode to authenticate with. Optional, typically set in chainspec so you don't have to pass it manually.

--webapp-url <WEBAPP_URL>

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.

--rpc-url <RPC_URL>

The URL to pass to the web app to connect to the node RPC.

If not passed, a URL with WebSocket scheme and localhost path will be used. Mutually exclusive with other options setting the RPC URL.

--rpc-url-ngrok-detect

Detect RPC URL from ngrok. This will also work with Humanode WebSocket Tunnel.

--rpc-url-ngrok-detect-from <TUNNEL_NAME>

The tunnel name at ngrok to detect RPC URL from, if ngrok is used to detect the RPC URL. [default: command_line]

--rpc-url-scheme-preference <RPC_URL_SCHEME_PREFERENCE>

What RPC URL scheme to prefer. [default: no-preference] [possible values: http, ws, no-preference]

--rpc-url-unset

Explicitly unset the RPC URL. Might be useful if you want to do something exotic, but generally, you'd want the RPC URL set.

Logonode-template | Substrate_ Docs