BITCOIN-TX(1)

📦
version 31.1 · 7 versions
, in epel 10, fedora 43, fedora 44

✨ BITCOIN-TX ✨

okay bestie, welcome to bitcoin-tx — it's a User Commands girlie, it lives in section 1 of the manual, and it is literally the manual page for bitcoin-tx v31.1.0. pull up a chair 💖

🌸 NAME 🌸

bitcoin-tx — the manual page for bitcoin-tx v31.1.0, no cap

🎀 SYNOPSIS 🎀

bitcoin-tx [options] <hex-tx> [commands]
bitcoin-tx [options] -create [commands]

💅 DESCRIPTION 💅

so this is the Bitcoin Core bitcoin-tx utility, version v31.1.0. it's giving utility. it's giving transaction wizardry.

the bitcoin-tx tool is what you use for creating and modifying bitcoin transactions. main character energy fr.

you can run it two ways:

  • with "<hex-tx> [commands]" to update a hex-encoded bitcoin transaction
  • with "-create [commands]" to create a hex-encoded bitcoin transaction

that's it, that's the vibe 🦋

✨ OPTIONS ✨

  • -create — make a brand new, empty TX. a little blank canvas, an empty nest, a fresh start 🥚
  • -help — print this help message and dip (also works as -h or -?)
  • -json — pick JSON output, bestie. the structured girlie option
  • -txid — output only the hex-encoded transaction id of the resultant transaction. just the id. nothing else. she's minimal like that
  • -version — print version and exit

🔧 Debugging/Testing options:

okay so this heading is here in the original and there's genuinely nothing under it. iconic of her. we respect it. ✨

⛓️ Chain selection options:

  • -chain=<chain> — use the chain <chain> (default: main). the allowed values are main, test, testnet4, signet, regtest. pick your universe 🪐
  • -signet — use the signet chain. equivalent to -chain=signet. heads up though: 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 testnet3 chain. equivalent to -chain=test.
⚠️ not to be dramatic but: support for testnet3 is deprecated and will be removed in an upcoming release. consider moving to testnet4 now by using -testnet4. like, actually consider it 🫶
  • -testnet4 — use the testnet4 chain. equivalent to -chain=testnet4.

🌈 Commands:

  • delin=N — delete input N from TX. bye girl 👋
  • 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 — add address-based output to TX
  • outdata=[VALUE:]DATA — add data-based output to TX
  • outmultisig=VALUE:REQUIRED:PUBKEYS:PUBKEY1:PUBKEY2:....[:FLAGS] — add a 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. multi-sig said let me do it for you 💜
  • 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) — sets the Replace-By-Fee (RBF) opt-in sequence number for input N. if N isn't provided, the command attempts to opt-in all available inputs for RBF. if the transaction has no inputs, this option is ignored. RBF girlies stay winning 🔥
  • sign=SIGHASH-FLAGS — add zero or more signatures to transaction. this command requires JSON registers: prevtxs=JSON object, privatekeys=JSON object. see the signrawtransactionwithkey docs for the format of sighash flags and JSON objects.

📝 Register Commands:

  • load=NAME:FILENAME — load JSON file FILENAME into register NAME
  • set=NAME:JSON-STRING — set register NAME to the given JSON-STRING

Copyright (C) 2009-2026 The Bitcoin Core developers

please contribute if you find Bitcoin Core useful!! visit <https://bitcoincore.org/> for further information about the software. the source code is available from <https://github.com/bitcoin/bitcoin>. 🫶

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

🦋 SEE ALSO 🦋

k that's the whole page bestie, go forth and build transactions 💖✨ this was bitcoin-tx v31.1.0, dated July 2026, and yes the page name really is BITCOIN-TX(1) — ily, mwah 🎀💅

📦 where this page comes from