BITCOIN-TX(1)

📦 version 0.18.0, in nixpkgs unstable

💅 bitcoin-tx — the manual, but make it make sense 💅

okay so bestie, this is the official manual page for bitcoin-tx from v0.21.2.0 — it's a lil' User Commands situation and honestly it's giving utility belt energy. let me walk you through it fr fr 💖

✨ NAME ✨

bitcoin-tx — manual page for bitcoin-tx v0.21.2.0

like, that's literally the whole name section. iconic of them tbh. 🎀

🦋 SYNOPSIS 🦋

okay so there are exactly two ways to run this thing, and here they are:

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

first one updates a hex-encoded bitcoin transaction, second one creates a hex-encoded bitcoin transaction. pick your fighter, bestie 💅

🌸 DESCRIPTION 🌸

Bitcoin Core bitcoin-tx utility version v0.21.2.0

that's it. that's the whole description. no notes. ✨

👑 OPTIONS 👑

okay here comes the good stuff, buckle up buttercup:

  • -? — Print this help message and exit. the classic "help me bestie" flag 🫶
  • -create — Create new, empty TX. a whole blank canvas, no cap.
  • -json — Select JSON output. for when you want your data all dressed up cute in JSON 💖
  • -txid — Output only the hex-encoded transaction id of the resultant transaction. minimal era.

🛠️ Debugging/Testing options:

(no cap, this heading is just there with nothing under it in the original — keeping it exactly as-is because I don't make the rules, I just vibe with them 💀)

🔗 Chain selection options:

  • -chain=<chain> — Use the chain <chain> (default: main). Allowed values: main, test, signet, regtest. pick your timeline bestie ⭐
  • -signet — Use the signet chain. Equivalent to -chain=signet. Note that the network is defined by the -signetchallenge parameter. ok so signet's whole personality is defined elsewhere, noted. 🌈
  • -signetchallenge — Blocks must satisfy the given script to be considered valid (only for signet networks; defaults to the global default signet test network challenge). like a vibe check for blocks, literally. 🦋
  • -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)). so sig.net:1234 is the example, and yes you can stack these, queen. 👑
  • -testnet — Use the test chain. Equivalent to -chain=test. test mode era 🧪

🎀 Commands 🎀

okay these are the actual commands you can throw at it, one by one, no skips:

  • delin=N — Delete input N from TX. bye felicia to input N 👋
  • delout=N — Delete output N from TX. same energy, but for outputs 💀
  • in=TXID:VOUT(:SEQUENCE_NUMBER) — Add input to TX. add that input, bestie 🫶
  • locktime=N — Set TX lock time to N. lock it in. periodt.
  • nversion=N — Set TX version to N. version upgrade, slay.
  • outaddr=VALUE:ADDRESS — Add address-based output to TX. 📬
  • outdata=[VALUE:]DATA — Add data-based output to TX. data girlie 💾
  • 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. multsig is so extra and I respect it 💅
  • 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. raw and unfiltered, love that for it 📜
  • replaceable(=N) — Set RBF opt-in sequence number for input N (if not provided, opt-in all available inputs). RBF era, we love a replaceable king 🔥
  • 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. get them signatures bestie ✍️

📋 Register Commands:

  • load=NAME:FILENAME — Load JSON file FILENAME into register NAME. loading era 💾
  • set=NAME:JSON-STRING — Set register NAME to given JSON-STRING. set it and forget it ✨

Copyright (C) 2009-2020 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>.

⚠️ okay listen bestie this part is important: This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/licenses/MIT>. experimental = handle with care, no cap 🙈

and that's the whole thing! 💖 this was bitcoin-tx v0.21.2.0, dated August 2021, and honestly she ate. go forth and build your transactions bestie, you got this 🫶✨🌸

📦 where this page comes from