DIGIBYTE-CLI(1)
Manual name: DIGIBYTE-CLI(1) β User Commands, but make it main-character energy. Okay bestie, buckle up: this page is a double feature, because the original is giving two snapshots stitched together. First up is the v0.15.0.1 era from September 2017, then the v0.17.1.0 glow-up from December 2018. Every flag and fact stays exactly as it was β I'm just here to make it make sense. π
π NAME π
digibyte-cli β manual page for digibyte-cli v0.15.0.1.
This is the first NAME block, no cap.
π DESCRIPTION π
DigiByte Core RPC client version v0.15.0.1-dirty
Okay so this is the RPC client for DigiByte Core, and the version string is literally v0.15.0.1-dirty. The old usage block goes a little like this β and yes, the original is showing conflict-marker realness, so I'm keeping it exactly:
digibyte-cli [options] <command> [params]
Send command to DigiByte Core =======
digibyte-cli [options] -named <command> [name=value] ... Send
command to DigiByte Core (with named arguments) digibyte-cli
[options] help List commands digibyte-cli
[options] help <command> Get help for a command =======
>>>>>>> e97f9575d305be3bae99eb731045ebf411582f49 =======
That first snapshot signs off with digibyte-cli v0.15.0.1 β September 2017, and then the page hits a divider and moves on. Iconic.
π¦ NAME π¦
digibyte-cli β manual page for digibyte-cli v0.17.1.0.
β¨ SYNOPSIS β¨
digibyte-cli [options] <command> [params] Send command to DigiByte Core
digibyte-cli [options] -named <command> [name=value]... Send command to
DigiByte Core (with named arguments)
digibyte-cli [options] help List commands
digibyte-cli [options] help <command> Get help for a command
πΈ DESCRIPTION πΈ
DigiByte Core RPC client version v0.17.1.0 >>>>>>> 0.17:doc/man/bitcoin-cli.1
Yup, that line is exactly what the original says, conflict marker and all. It's giving "we merged the docs and left the evidence" but we move.
π OPTIONS π
Okay bestie, here's the full menu. No skips.
-?β The classic: this help message. A little question mark that says "help me help you."-conf=<file>β Pick your configuration file. Relative paths will be prefixed by thedatadirlocation.(default: digibyte.conf)-datadir=<dir>β Specify data directory. That's the home base for your data.-getinfoβ Get general information from the remote server. Important caveat, bestie: note that unlike server-side RPC calls, the results of-getinfois the result of multiple non-atomic requests. Some entries in the result may represent results from different states (e.g. wallet balance may be as of a different block from the chain state reported). So yeah, it's a vibe collage, not a single atomic snapshot.-namedβ Pass named instead of positional arguments.(default: false)-rpcclienttimeout=<n>β Timeout in seconds during HTTP requests, or0for no timeout.(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 will be prefixed by a net-specificdatadirlocation.(default: data dir)-rpcpassword=<pw>β Password for JSON-RPC connections. Keep it secret, keep it safe. π«Ά-rpcport=<port>β Connect to JSON-RPC on<port>.(default: 8332 or testnet: 18332)-rpcuser=<user>β Username for JSON-RPC connections.-rpcwaitβ Wait for the RPC server to start. Patience is a virtue.-rpcwallet=<walletname>β Send RPC for a non-default wallet on the RPC server. This needs to exactly match the corresponding-walletoption passed todigibyted.-stdinβ Read extra arguments from standard input, one per line untilEOF/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.-versionβ Print version and exit. Slay.
βοΈ Chain selection options: βοΈ
-testnetβ Use the test chain.
π COPYRIGHT π
Copyright (C) 2009-2018 The DigiByte Core developers
Please contribute if you find DigiByte Core useful. Visit <https://digibytecore.org> for further information about the software. The source code is available from <https://github.com/digibyte/digibyte>.
This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/licenses/MIT>.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit <https://www.openssl.org> and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.
Okay that's the whole page, bestie. Final footer energy: digibyte-cli v0.17.1.0 β December 2018. Go forth and RPC responsibly. πβ¨
π¦ where this page comes from
- nixpkgs unstable: digibyted 7.17.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms