ELEMENTS-UTIL(1)

πŸ“¦
version 23.3.4 Β· 2 versions
, in nixpkgs unstable

πŸ’– ELEMENTS-UTIL(1) πŸ’–

okay bestie so this is elements-util, from manual page ELEMENTS-UTIL(1) β€” a manual page for elements-util v23.3.4, and it's giving "tiny utility, big secrets." sit down, grab a strawberry πŸ“, and let's go.


✨ SYNOPSIS ✨

bitcoin-util [options] [commands]  Do stuff

yes. "Do stuff." that's the whole pitch. iconic, honestly. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

Elements Core bitcoin-util utility version v23.3.4 β€” that's literally what it is. no notes. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

the basics, the essentials, the necessities

  • -? β€” prints this help message and dips. bye! πŸ‘‹
  • -version β€” prints the version and dips. same energy.

Debugging/Testing options:

so this heading exists and… it's empty, bestie. nothing under it. no cap. moving on. 🫢

Chain selection options:

  • -chain=<chain> β€” use the chain <chain>. default is liquidv1. the reserved values are: main, test, signet, regtest, liquidv1, liquidv1test, liquidtestnet. pick your fighter 🌈
  • -con_blockheightinheader β€” whether the chain includes the block height directly in the header, for easier validation of block height in low-resource environments. default: 1. lowkey so considerate πŸ’–
  • -con_has_parent_chain β€” whether or not there is a parent chain. that's it. that's the whole thing. do you have a parent chain or not, bestie 😭
  • -con_max_block_sig_size β€” max allowed witness data for the signed block header.
  • -con_parent_chain_signblockscript β€” whether the parent chain uses pow or signed blocks. if the parent chain uses signed blocks, this is the challenge (scriptPubKey) script. if not, it's an empty string. default: empty script [ie parent uses pow].
  • -con_parentpowlimit β€” the proof-of-work limit value for the parent chain. ⚑
  • -con_signed_blocks β€” signed blockchain. uses input of -signblockscript to define what signatures are necessary to solve it.
  • -fedpegscript β€” the script for the federated peg enforce from genesis block. this script may stop being enforced once dynamic federations activates. heads up fr 🫑
  • -parentgenesisblockhash β€” the genesis blockhash of the parent chain.
  • -signblockscript β€” signed blockchain enumberance. only active when -con_signed_blocks set to true. (yes, "enumberance" β€” we do not fix typos in this house, we preserve them like pressed flowers 🌸)
  • -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). collect them all 🧚
  • -testnet β€” use the test chain. equivalent to -chain=test.

Elements Options:

  • -acceptunlimitedissuances β€” allow unblinded issuance amounts to exceed 21 million units. unblinded!! exceeding 21 million!!! bestie be so careful with this one 😭
  • -con_blocksubsidy β€” defines the amount of block subsidy to start with, at genesis block, in satoshis.
  • -con_connect_genesis_outputs β€” connect outputs in genesis block to utxo database.
  • -con_csv_deploy_start β€” starting height for CSV deployment. default: -1, which means ACTIVE from genesis. love a dramatic all-caps default ✨
  • -con_dyna_deploy_signal β€” whether to signal for the Dynamic Federations deployment. default: 1.
  • -con_elementsmode β€” use Elements-like instead of Core-like witness encoding. this is required for CA/CT. default: 1.
  • -con_mandatorycoinbase β€” all non-zero valued coinbase outputs must go to this scriptPubKey, if set.
  • -dynamic_epoch_length β€” per-chain parameter that sets how many blocks dynamic federation voting and enforcement are in effect for.
  • -enforce_pak β€” causes standardness checks to enforce Pegout Authorization Key(PAK) validation before dynamic federations, and consensus enforcement after. πŸ”₯
  • -multi_data_permitted β€” allow relay of multiple OP_RETURN outputs. default: -enforce_pak.
  • -pak β€” sets the 'first extension space' field to the pak entries ala pre-dynamic federations. only used for testing in custom chains.
  • -total_valid_epochs β€” per-chain parameter that sets how long a particular fedpegscript is in effect for.

Commands:

  • grind β€” perform proof of work on hex header string. go off, king πŸ’€βš‘

Copyright (C) 2009-2026 The Elements Project developers Copyright (C) 2009-2026 The Bitcoin Core developers

please contribute if you find Elements Core useful, bestie β€” visit <https://elementsproject.org/> for further information about the software. the source code is available from <https://github.com/ElementsProject/elements>. 🫢

this is experimental software. distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/licenses/MIT>. experimental, okay?? treat it with respect πŸ™ˆ

and that's the whole vibe. this page is elements-util v23.3.4, dated September 2026, footer says ELEMENTS-UTIL(1) β€” slay, stay safe, and read your COPYING file πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from