.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.48.5. .TH ELEMENTS-CLI "1" "March 2022" "elements-cli 0.21.0.2" "User Commands" .SH NAME elements-cli \- manual page for elements-cli 0.21.0.2 .SH SYNOPSIS .B elements-cli [\fI\,options\/\fR] \fI\, \/\fR[\fI\,params\/\fR] \fI\,Send command to Elements Core\/\fR .br .B elements-cli [\fI\,options\/\fR] \fI\,-named \/\fR[\fI\,name=value\/\fR]... \fI\,Send command to Elements Core (with named arguments)\/\fR .br .B elements-cli [\fI\,options\/\fR] \fI\,help List commands\/\fR .br .B elements-cli [\fI\,options\/\fR] \fI\,help Get help for a command\/\fR .SH DESCRIPTION Elements Core RPC client version elements\-0.21.0.2 .SH OPTIONS .HP \-? .IP Print this help message and exit .HP \fB\-conf=\fR .IP Specify configuration file. Relative paths will be prefixed by datadir location. (default: elements.conf) .HP \fB\-datadir=\fR .IP Specify data directory .HP \fB\-generate\fR .IP Generate blocks immediately, equivalent to RPC generatenewaddress followed by RPC generatetoaddress. Optional positional integer arguments are number of blocks to generate (default: 1) and maximum iterations to try (default: 1000000), equivalent to RPC generatetoaddress nblocks and maxtries arguments. Example: bitcoin\-cli \fB\-generate\fR 4 1000 .HP \fB\-getinfo\fR .IP Get general information from the remote server. Note that unlike server\-side RPC calls, the results of \fB\-getinfo\fR is 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) .HP \fB\-named\fR .IP Pass named instead of positional arguments (default: false) .HP \fB\-netinfo\fR .IP Get network peer connection information from the remote server. An optional integer argument from 0 to 4 can be passed for different peers listings (default: 0). .HP \fB\-rpcclienttimeout=\fR .IP Timeout in seconds during HTTP requests, or 0 for no timeout. (default: 900) .HP \fB\-rpcconnect=\fR .IP Send commands to node running on (default: 127.0.0.1) .HP \fB\-rpccookiefile=\fR .IP Location of the auth cookie. Relative paths will be prefixed by a net\-specific datadir location. (default: data dir) .HP \fB\-rpcpassword=\fR .IP Password for JSON\-RPC connections .HP \fB\-rpcport=\fR .IP Connect to JSON\-RPC on (default: 7041, testnet: 18332, signet: 38332, regtest: 18443) .HP \fB\-rpcuser=\fR .IP Username for JSON\-RPC connections .HP \fB\-rpcwait\fR .IP Wait for RPC server to start .HP \fB\-rpcwallet=\fR .IP Send RPC for non\-default wallet on RPC server (needs to exactly match corresponding \fB\-wallet\fR option passed to elementsd). This changes the RPC endpoint used, e.g. http://127.0.0.1:8332/wallet/ .HP \fB\-stdin\fR .IP Read extra arguments from standard input, one per line until EOF/Ctrl\-D (recommended for sensitive information such as passphrases). When combined with \fB\-stdinrpcpass\fR, the first line from standard input is used for the RPC password. .HP \fB\-stdinrpcpass\fR .IP Read RPC password from standard input as a single line. When combined with \fB\-stdin\fR, the first line from standard input is used for the RPC password. When combined with \fB\-stdinwalletpassphrase\fR, \fB\-stdinrpcpass\fR consumes the first line, and \fB\-stdinwalletpassphrase\fR consumes the second. .HP \fB\-stdinwalletpassphrase\fR .IP Read wallet passphrase from standard input as a single line. When combined with \fB\-stdin\fR, the first line from standard input is used for the wallet passphrase. .HP \fB\-version\fR .IP Print version and exit .PP Debugging/Testing options: .PP Chain selection options: .HP \fB\-chain=\fR .IP Use the chain (default: liquidv1). Reserved values: main, test, signet, regtest, liquidv1, liquidv1test .HP \fB\-con_blockheightinheader\fR .IP Whether the chain includes the block height directly in the header, for easier validation of block height in low\-resource environments. (default: true) .HP \fB\-con_has_parent_chain\fR .IP Whether or not there is a parent chain. .HP \fB\-con_max_block_sig_size\fR .IP Max allowed witness data for the signed block header. .HP \fB\-con_parent_chain_signblockscript\fR .IP Whether parent chain uses pow or signed blocks. If the parent chain uses signed blocks, the challenge (scriptPubKey) script. If not, an empty string. (default: empty script [ie parent uses pow]) .HP \fB\-con_parentpowlimit\fR .IP The proof\-of\-work limit value for the parent chain. .HP \fB\-con_signed_blocks\fR .IP Signed blockchain. Uses input of `\-signblockscript` to define what signatures are necessary to solve it. .HP \fB\-fedpegscript\fR .IP The script for the federated peg enforce from genesis block. This script may stop being enforced once dynamic federations activates. .HP \fB\-parentgenesisblockhash\fR .IP The genesis blockhash of the parent chain. .HP \fB\-signblockscript\fR .IP Signed blockchain enumberance. Only active when `\-con_signed_blocks` set to true. .HP \fB\-signet\fR .IP Use the signet chain. Equivalent to \fB\-chain\fR=\fI\,signet\/\fR. Note that the network is defined by the \fB\-signetchallenge\fR parameter .HP \fB\-signetchallenge\fR .IP Blocks must satisfy the given script to be considered valid (only for signet networks; defaults to the global default signet test network challenge) .HP \fB\-signetseednode\fR .IP 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)) .HP \fB\-testnet\fR .IP Use the test chain. Equivalent to \fB\-chain\fR=\fI\,test\/\fR. .PP Elements Options: .HP \fB\-con_blocksubsidy\fR .IP Defines the amount of block subsidy to start with, at genesis block, in satoshis. .HP \fB\-con_connect_genesis_outputs\fR .IP Connect outputs in genesis block to utxo database. .HP \fB\-con_csv_deploy_start\fR .IP Starting height for CSV deployment. (default: \fB\-1\fR, which means ACTIVE from genesis) .HP \fB\-con_dyna_deploy_signal\fR .IP Whether to signal for the Dynamic Federations deployment (default: true). .HP \fB\-con_elementsmode\fR .TP Use Elements\-like instead of Core\-like witness encoding. This is .IP required for CA/CT. (default: true) .HP \fB\-con_mandatorycoinbase\fR .IP All non\-zero valued coinbase outputs must go to this scriptPubKey, if set. .HP \fB\-dynamic_epoch_length\fR .IP Per\-chain parameter that sets how many blocks dynamic federation voting and enforcement are in effect for. .HP \fB\-enforce_pak\fR .IP Causes standardness checks to enforce Pegout Authorization Key(PAK) validation before dynamic federations, and consensus enforcement after. .HP \fB\-multi_data_permitted\fR .IP Allow relay of multiple OP_RETURN outputs. (default: \fB\-enforce_pak\fR) .HP \fB\-pak\fR .IP Sets the 'first extension space' field to the pak entries ala pre\-dynamic federations. Only used for testing in custom chains. .HP \fB\-total_valid_epochs\fR .IP Per\-chain parameter that sets how long a particular fedpegscript is in effect for. .SH COPYRIGHT Copyright (C) 2009-2021 The Elements Project developers Copyright (C) 2009-2021 The Bitcoin Core developers Please contribute if you find Elements Core useful. Visit for further information about the software. The source code is available from . This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or