ELEMENTS-TX(1)

📦
version 23.3.4 · 2 versions
, in nixpkgs unstable

💅 ELEMENTS-TX(1) — the elements-tx glow-up ✨

okay so bestie, this is the manual page for elements-tx — it's a User Command, and it literally lives in the ELEMENTS-TX(1) section of the man pages, iykyk. buckle up 🎀

🌸 NAME 🌸

elements-tx — manual page for elements-tx v23.3.4

⭐ SYNOPSIS ⭐

elements-tx [options] <hex-tx> [commands]  Update hex-encoded Elements
transaction
elements-tx [options] -create [commands]   Create hex-encoded Elements
transaction

so like, two whole moods 💖 — you're either updating a hex-encoded Elements transaction, or you're creating one from scratch with -create. pick your fighter 🫶

🦋 DESCRIPTION 🦋

Elements Core elements-tx utility version v23.3.4

that's it. that's the description. short and iconic 👑

✨ OPTIONS ✨

  • -? — prints this help message and then dips out, exit stage left 💅
  • -create — makes a brand new, empty TX. blank canvas energy 🎨
  • -json — picks JSON output. fancy formatting unlocked ✨
  • -txid — outputs only the hex-encoded transaction id of the resultant transaction. just the id, nothing else, main character only 👑
  • -version — prints the version and exits 🏃‍♀️

🔧 Debugging/Testing options:

ngl this section is literally just the heading in the original — no options listed under it, so don't come for me 🙈 moving on!

⛓️ Chain selection options:

  • -chain=<chain> — use the chain <chain> (default: liquidv1). reserved values are: main, test, signet, regtest, liquidv1, liquidv1test, liquidtestnet 👀 pick wisely
  • -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) 🧠
  • -con_has_parent_chain — whether or not there is a parent chain. simple as that, bestie 👩‍👧
  • -con_max_block_sig_size — max allowed witness data for the signed block header 📏
  • -con_parent_chain_signblockscript — 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]) 🔐
  • -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 🫶
  • -parentgenesisblockhash — the genesis blockhash of the parent chain 🧬
  • -signblockscript — signed blockchain enumberance. only active when -con_signed_blocks set to true ⚡
  • -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 test chain. equivalent to -chain=test. 🧪

💎 Elements Options:

  • -acceptunlimitedissuances — allow unblinded issuance amounts to exceed 21 million units 😳 yes, unlimited, no cap (literally)
  • -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) 🚀
  • -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:

  • delin=N — delete input N from TX ✂️
  • delout=N — delete output N from TX 🗑️
  • in=TXID:VOUT(:SEQUENCE_NUMBER) — add input to TX ➕
  • locktime=N — set TX lock time to N 🔒
  • nversion=N — set TX version to N 🔢
  • outaddr=VALUE:ADDRESS(:ASSET) — add address-based output to TX 📮
  • outdata=[VALUE:]DATA — add data-based output to TX 💾
  • outmultisig=VALUE:REQUIRED:PUBKEYS:PUBKEY1:PUBKEY2:....[:FLAGS] — add Pay To n-of-m Multi-sig output to TX. n = REQUIRED, m = PUBKEYS. optionally add the "W" flag to produce a pay-to-witness-script-hash output. optionally add the "S" flag to wrap the output in a pay-to-script-hash 🔑
  • outpubkey=VALUE:PUBKEY[:FLAGS] — add pay-to-pubkey output to TX. optionally add the "W" flag to produce a pay-to-witness-pubkey-hash output. optionally add the "S" flag to wrap the output in a pay-to-script-hash 🗝️
  • outscript=VALUE:SCRIPT[:FLAGS] — add raw script output to TX. optionally add the "W" flag to produce a pay-to-witness-script-hash output. optionally add the "S" flag to wrap the output in a pay-to-script-hash 📜
  • replaceable(=N) — set RBF opt-in sequence number for input N (if not provided, opt-in all available inputs) 🔁
  • sign=SIGHASH-FLAGS — add zero or more signatures to transaction. this command requires JSON registers: prevtxs=JSON object, privatekeys=JSON object. see signrawtransactionwithkey docs for format of sighash flags, JSON objects ✍️

🧚 Register Commands:

  • -serialization=TYPE — sets the serialization of transactions. ELEMENTS or BITCOIN are the two valid options 🎚️
  • load=NAME:FILENAME — load JSON file FILENAME into register NAME 📂
  • set=NAME:JSON-STRING — set register NAME to given JSON-STRING 🧾

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>. 🫶

⚠️ heads up bestie: this is experimental software. distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/licenses/MIT> 📄

okay and like, the cutest little sign-off ever 💖 this whole page is from elements-tx v23.3.4, dated September 2026, and it's filed under ELEMENTS-TX(1) — so now you know, and honestly? slay. periodt. 🌈✨🎀

📦 where this page comes from