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
  1. Node
  2. CLI

Dev Mode

The page describes a basic approach to run humanode-peer in dev mode.

The dev chain should be specified to run the node in dev mode:

humanode-peer --dev

In development mode, the chain doesn't require any peer computers to produce and finalize blocks. If you see messages that blocks are being proposed and finalized, you have a running node.

... Idle (0 peers), best: #3 (0xcc78…5cb1), finalized #1 ...
... Starting consensus session on top of parent ...
... Prepared block for proposing at 4 (0 ms) ...

Additionally, --tmp flag can be passed to indicate that the node should be run as a temporary node. A temporary directory will be created to store the configuration and will be deleted at the end of the process.

humanode-peer --dev --tmp
PreviousCLINextJSON-RPC

Last updated 2 months ago