NAMECOIN-CLI(1)

📦
version 32.0 · 2 versions
, in nixpkgs unstable

💖 namecoin-cli(1) — the manual, but make it group chat 💖

okay so bestie, welcome to namecoin-cli, from the User Commands corner of the manual-verse, part of Namecoin Core, version v32.0.0 ✨ this is the command-line bestie that talks to your Namecoin node so you don't have to.

🌸 NAME 🌸

namecoin-cli — literally the manual page for namecoin-cli v32.0.0, no cap 🫶

✨ SYNOPSIS ✨

namecoin-cli [options] <command> [params]
namecoin-cli [options] -named <command> [name=value]...
namecoin-cli [options] help
namecoin-cli [options] help <command>

Four whole ways to summon her, pick your fighter 💅

🦋 DESCRIPTION 🦋

Namecoin Core RPC client, version v32.0.0 — yes that's the whole personality, and honestly? iconic.

The namecoin-cli utility is your little command line interface bestie for talking to a Namecoin Core RPC server. She's the go-between 🧚

What can she do for you? Query network information, manage wallets, create or broadcast transactions, and control the Namecoin Core server. main character energy fr fr 👑

Use the "help" command to list all commands. Use "help <command>" to show help for that specific command. And the -named option lets you specify parameters using the key=value format — which is a whole slay, because it means you don't have to pass unused positional parameters. no more awkward empty slots 🎀

💜 OPTIONS 💜

  • -color=<when> — the color setting for CLI output (default: auto). Valid values: always, auto (which adds color codes when standard output is connected to a terminal and the OS is not WIN32), and never. Heads up: only applies to the output of -getinfo. 🎨
  • -conf=<file> — specify the configuration file. Relative paths get prefixed by the datadir location. (default: namecoin.conf)
  • -datadir=<dir> — specify the data directory 📁
  • -help — print this help message and exit (also works as -h or -?) 🙋‍♀️
  • -named — pass named instead of positional arguments (default: false)
  • -rpcclienttimeout=<n> — timeout in seconds during HTTP requests, or 0 for no timeout. Not implemented for IPC connections (see -ipcconnect). (default: 900) ⏰
  • -rpcconnect=<ip> — send commands to the node running on <ip> (default: 127.0.0.1)
  • -rpccookiefile=<loc> — location of the auth cookie. Relative paths get prefixed by a net-specific datadir location. (default: data dir) 🍪
  • -rpcid=<id> — set a custom JSON-RPC request ID string (default: 1)
  • -rpcpassword=<pw> — password for JSON-RPC connections 🔐
  • -rpcport=<port> — connect to JSON-RPC on <port> (default: 8336, testnet: 18336, testnet4: 48336, signet: 38336, regtest: 18443)
  • -rpcuser=<user> — username for JSON-RPC connections
  • -rpcwait — wait for the RPC server to start ⏳
  • -rpcwaittimeout=<n> — timeout in seconds to wait for the RPC server to start, or 0 for no timeout. (default: 0)
  • -rpcwallet=<walletname> — send the RPC for a non-default wallet on the RPC server (needs to exactly match the corresponding -wallet option passed to namecoind). This changes the RPC endpoint used, e.g. http://127.0.0.1:8332/wallet/<walletname> 👛
  • -stdin — read extra arguments from standard input, one per line until EOF/Ctrl-D. Recommended for sensitive information such as passphrases! When combined with -stdinrpcpass, the first line from standard input is used for the RPC password. 🤫
  • -stdinrpcpass — read the RPC password from standard input as a single line. When combined with -stdin, the first line from standard input is used for the RPC password. When combined with -stdinwalletpassphrase, -stdinrpcpass consumes the first line, and -stdinwalletpassphrase consumes the second. line economy 🫶
  • -stdinwalletpassphrase — read the wallet passphrase from standard input as a single line. When combined with -stdin, the first line from standard input is used for the wallet passphrase.
  • -version — print version and exit ⭐

🔧 Debugging/Testing options: 🔧

okay so this heading is here and she's serving absolutely nothing underneath — no options listed in the original. still keeping her, because completeness is the vibe 💀

⛓️ Chain selection options: ⛓️

  • -chain=<chain> — use the chain <chain> (default: main). Allowed values: main, test, testnet4, signet, regtest 🌈
  • -signet — use the signet chain. Equivalent to -chain=signet. Note that the network is defined by the -signetchallenge parameter.
  • -signetchallenge — blocks must satisfy the given script to be considered valid (only for signet networks; defaults to the global default signet test network challenge) 🔥
  • -signetseednode — specify a seed node for the signet network, in the hostname[:port] format, e.g. sig.net:1234 (may be used multiple times to specify multiple seed nodes; defaults to the global default signet test network seed node(s)) 🌱
  • -testnet — use the testnet3 chain. Equivalent to -chain=test. > Support for testnet3 is deprecated and will be removed in an upcoming release. Consider moving to testnet4 now by using -testnet4. please don't ignore this bestie 😭
  • -testnet4 — use the testnet4 chain. Equivalent to -chain=testnet4. ✨

💅 CLI Commands: 💅

  • -addrinfo — get the number of addresses known to the node, per network and total.
  • -generate — generate blocks! Equivalent to RPC getnewaddress followed by RPC generatetoaddress. Optional positional integer arguments are the number of blocks to generate (default: 1) and the maximum iterations to try (default: 1000000), equivalent to RPC generatetoaddress nblocks and maxtries arguments. Example:
namecoin-cli -generate 4 1000
  • -getinfo — get general information from the remote server. Note that unlike server-side RPC calls, the output of -getinfo is the result of multiple non-atomic requests. Some entries in the output may represent results from different states (e.g. wallet balance may be as of a different block from the chain state reported). so like, read it with love but also with caution 🙈
  • -netinfo — get network peer connection information from the remote server. An optional argument from 0 to 4 can be passed for different peers listings (default: 0). If a non-zero value is passed, an additional "outonly" (or "o") argument can be passed to see outbound peers only. Pass "help" (or "h") for detailed help documentation. 👀

🧚 IPC interprocess connection options: 🧚

  • -ipcconnect=<address> — connect to bitcoin-node through an IPC socket instead of a TCP socket to execute requests. Valid <address> values are 'auto' to try to connect to the default socket path at <datadir>/node.sock but fall back to TCP if it's not available, 'unix' to connect to the default socket and fail if it isn't available, or 'unix:<socket path>' to connect to a socket at a nonstandard path. -noipcconnect can be specified to avoid attempting to use IPC at all. Default value: auto 🔌

Copyright (C) 2009-2026 The Namecoin Core developers

Please contribute if you find Namecoin Core useful — she's asking nicely 🫶 Visit <https://namecoin.org/> for further information about the software. The source code is available from <https://github.com/namecoin/namecoin-core>.

This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/license/MIT> 📜

🌈 SEE ALSO 🌈

namecoind(1), namecoin-cli(1), namecoin-tx(1), namecoin-wallet(1), namecoin-util(1), namecoin-qt(1) — the whole friend group, go say hi 💖

that's the whole page bestie, you ate 💅 this was namecoin-cli v32.0.0, dated October 2026, signing off with a 🎀 and a promise that you now know more than you did five minutes ago. periodt. ✨

📦 where this page comes from