DIGIBYTE-TX(1)

💅 digibyte-tx — the manual page, but make it cute

okay so bestie, welcome to digibyte-tx(1) — it's a User Command, it lives in section 1 of the manual, and it's literally the digibyte-tx glow-up utility from DigiByte Core. 💖

---

✨ SYNOPSIS ✨

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

Two moods, same icon: either you're updating a hex-encoded digibyte transaction (drop the hex in, stack commands on top), or you're creating one from absolutely nothing with -create. Both take [options] and both take [commands]. periodt. ✨

---

🌸 DESCRIPTION 🌸

It's the DigiByte Core digibyte-tx utility, version v0.17.1.0. That's the whole description, and honestly? She said what she said. 🫶

---

🎀 OPTIONS 🎀

• -? — the help message. Your "bestie what does this do" button. 🙈
• -create — create a new, empty TX. A blank canvas. main character energy from day one. 🦋
• -json — select JSON output. give me structure, give me curly braces. 👑
• -txid — output only the hex-encoded transaction id of the resultant transaction. no notes, just the id. 💅

🔥 Chain selection options 🔥

• -testnet — use the test chain. rehearsal era. 🌈

⭐ Commands ⭐

• delin=N — delete input N from the TX. bye bestie 👋
• delout=N — delete output N from the TX. also bye 👋
• in=TXID:VOUT(:SEQUENCE_NUMBER) — add an input to the TX. (yes, the SEQUENCE_NUMBER bit is optional, the parens said so)
• locktime=N — set the TX lock time to N.
• nversion=N — set the TX version to N.
• outaddr=VALUE:ADDRESS — add an address-based output to the TX.
• outdata=[VALUE:]DATA — add a data-based output to the TX. VALUE optional, data mandatory, we love a low-maintenance parameter.
• outmultisig=VALUE:REQUIRED:PUBKEYS:PUBKEY1:PUBKEY2:....[:FLAGS] — add a Pay To n-of-m Multi-sig output to the TX. here's the math, bestie: 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. two flags, two vibes. 💜
• outpubkey=VALUE:PUBKEY[:FLAGS] — add a pay-to-pubkey output to the 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 a raw script output to the 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 the RBF opt-in sequence number for input N. if N isn't provided, it opts in all available inputs — yes, all of them, no cap. 🔥
• sign=SIGHASH-FLAGS — add zero or more signatures to the transaction. this command requires the JSON registers prevtxs=JSON object and privatekeys=JSON object. for the format of sighash flags and those JSON objects, see the signrawtransaction docs. (iykyk 📚)

🧚 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 👑

Copyright (C) 2009-2018 The DigiByte Core developers 💖

Please contribute if you find DigiByte Core useful — fr fr, they're asking nicely. Visit <https://digibytecore.org> for more info about the software. The source code is available from <https://github.com/digibyte/digibyte>. 🫶

This is experimental software. Distributed under the MIT software license — see the accompanying file COPYING or <https://opensource.org/licenses/MIT>. experimental, bestie, so like… be aware. 💀

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit <https://www.openssl.org>, plus cryptographic software written by Eric Young and UPnP software written by Thomas Bernard. shoutout to the legends. 🌟

---

and that's the whole page, no skips, no summaries — 🎀 this has been digibyte-tx v0.17.1.0, dated December 2018, signing off from the DIGIBYTE-TX(1) section of the manual. slay, stay hex-encoded, and hydrate. 💜✨