ELEMENTS-WALLET(1)

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

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

okay so bestie, welcome to the elements-wallet glow-up page πŸ’… this is the manual for elements-wallet, and yes it's a real one, from the User Commands section, no cap.


✨ NAME ✨

elements-wallet β€” literally the manual page for elements-wallet v23.3.4, she's an icon, she's a legend, and she's right here πŸŽ€


🌸 DESCRIPTION 🌸

This is Elements Core elements-wallet version v23.3.4 πŸ’œ

So what is she? elements-wallet is an offline tool for creating and interacting with Elements Core wallet files β€” offline, meaning she's not out here gossiping with the network, she's just handling her business locally 🧚

By default, elements-wallet acts on wallets in the default mainnet wallet directory in the datadir. That's the default vibe. But if you wanna change the target wallet (and honestly, valid), you use the -datadir, -wallet and -regtest/-signet/-testnet arguments ✨

πŸ¦‹ Usage:

elements-wallet [options] <command>

That's it. Options first, command after. Slay.


πŸ‘‘ OPTIONS πŸ‘‘

🌈 The main-character options

  • -? β€” prints this help message and dips. exit stage left 🫢
  • -datadir=<dir> β€” specify the data directory, aka where she keeps her stuff.
  • -descriptors β€” creates a descriptors wallet. Only for create, okay?? only for create πŸ’…
  • -dumpfile=<file name> β€” when you use it with dump, she writes out the records to this file. When you use it with createfromdump, she loads the records into a new wallet. Two moods, one flag 😌
  • -format=<format> β€” the format of the wallet file to create. Either "bdb" or "sqlite". Only used with createfromdump. pick your fighter ⭐
  • -legacy β€” creates a legacy wallet. Only for create (yes, another one that's only for create, keep up bestie πŸŽ€)
  • -version β€” print version and exit. short, sweet, iconic.
  • -wallet=<wallet-name> β€” specify the wallet name. that's her name, use it πŸ’–

πŸ› Debugging/Testing options:

  • -debug=<category> β€” output debugging information (default: 0).
  • -printtoconsole β€” send trace/debug info to console (default: 1 when no -debug is true, 0 otherwise). yes, the default is conditional, she's ✨complex✨

⛓️ Chain selection options:

  • -chain=<chain> β€” use the chain <chain> (default: liquidv1). Reserved values: main, test, signet, regtest, liquidv1, liquidv1test, liquidtestnet. so many options, so little time 🌈
  • -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) β€” low-resource friendly, we love accessible validation πŸ’œ
  • -con_has_parent_chain β€” whether or not there is a parent chain. yes/no, she's asking πŸ¦‹
  • -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, the challenge (scriptPubKey) script. If not, 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. ⚠️ important detail, don't skip it ⚠️
  • -parentgenesisblockhash β€” the genesis blockhash of the parent chain.
  • -signblockscript β€” signed blockchain enumberance. Only active when -con_signed_blocks is set to true. (and yes, "enumberance" is what it says, I don't make the rules πŸ’€)
  • -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 like stickers πŸŽ€
  • -testnet β€” use the test chain. Equivalent to -chain=test.

πŸ’Ž Elements Options:

  • -acceptunlimitedissuances β€” allow unblinded issuance amounts to exceed 21 million units. 21 million who? not her, apparently πŸ™ˆ
  • -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) active from birth, main character energy πŸ‘‘
  • -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). required, bestie, not optional, read it again πŸ’…
  • -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. testing only, don't be weird about it 🧚
  • -total_valid_epochs β€” per-chain parameter that sets how long a particular fedpegscript is in effect for.

πŸŽ€ Commands: πŸŽ€

  • create β€” create new wallet file. fresh start, new me ✨
  • createfromdump β€” create new wallet file from dumped records.
  • dump β€” print out all of the wallet key-value records.
  • info β€” get wallet info. she'll tell you everything πŸ’–
  • salvage β€” attempt to recover private keys from a corrupt wallet. Warning: salvage is experimental. 🚨 like, genuinely, it says experimental, so go in knowing that 🚨

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

Please contribute if you find Elements Core useful 🫢 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> πŸ’œ

okay that's the whole page, go forth and be iconic πŸŒˆπŸ’… and just so we're official: this was elements-wallet v23.3.4, dated September 2026, and the page itself is ELEMENTS-WALLET(1). mwah πŸ’‹ πŸŽ€

πŸ“¦ where this page comes from