NAMECOIN-TX(1)

📦 version 28.0, in nixos 26.05

💅 namecoin-tx(1) — the glow-up edition 💅

Okay so bestie, this is the manual page for namecoin-tx — the Namecoin Core namecoin-tx utility, version v28.0.0, and it's literally a little command-line gremlin that builds, edits, and signs raw hex transactions for you. No wallet GUI, no drama, just hex. Let's get into it 🫶

✨ SYNOPSIS ✨

Two moods, both iconic:

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

So either you're passing in an existing hex transaction and poking at it with commands, or you're spawning a brand new empty one with -create. Both slay 💅

🦋 DESCRIPTION 🦋

Namecoin Core namecoin-tx utility version v28.0.0 — that's the whole vibe. It's the transaction utility, it ships with Namecoin Core, and it does exactly what the synopsis said. Periodt.

💖 OPTIONS 💖

  • -? — prints this help message and dips. That's it, that's the whole job ✨
  • -create — creates a new, empty TX. Blank canvas energy 🎨
  • -json — picks JSON output. For when you want your data readable, ngl.
  • -nameencoding — the encoding to use for names in the JSON output (default: ascii). Yes, the default is ascii, bestie, don't come for me.
  • -txid — outputs only the hex-encoded transaction id of the resultant transaction. Nothing else. It's giving main character minimalism 👑
  • -valueencoding — the encoding to use for values in the JSON output (default: ascii).
  • -version — prints version and exits. Short and sweet, love that for you.

🔧 Debugging/Testing options:

That's genuinely the whole heading — there's nothing listed under it here. Not me leaving it in, it's literally in the original 😭

⛓️ Chain selection options:

  • -chain=<chain> — use the chain <chain> (default: main). Allowed values: main, test, testnet4, signet, regtest.
  • -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. > ⚠️ 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, she's on her way out 💀
  • -testnet4 — use the testnet4 chain. Equivalent to -chain=testnet4.

🎀 Commands:

These are the little spells you cast after your transaction, bestie:

  • 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.
  • namefirstupdate=N:NAME:VALUE:RAND — turns the existing output N into a NAME_FIRSTUPDATE operation with the given hex-encoded NAME, VALUE and RAND.
  • namenew=N:NAME:RAND — turns the existing output N into a NAME_NEW operation with the given hex-encoded NAME and RAND.
  • nameupdate=N:NAME:VALUE — turns the existing output N into a NAME_UPDATE operation with the given hex-encoded NAME and VALUE.
  • 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 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. Multisig but make it fashion ✨
  • 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 is not provided, the command attempts to opt-in all available inputs for RBF. If the transaction has no inputs, this option is ignored. No inputs, no problem, no notes 💀
  • 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. 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 (C) 2009-2024 The Bitcoin Core and Namecoin developers

Please contribute if you find Namecoin Core useful — that's a direct quote from the manpage and also just good manners 🫶 Visit https://www.namecoin.org/ for further information about the software. The source code is available from https://github.com/namecoin/namecoin-core.

⚠️ This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or https://opensource.org/licenses/MIT. Experimental, bestie — treat her with respect.

🌈 SEE ALSO 🌈

namecoind(1), namecoin-cli(1), namecoin-tx(1), namecoin-wallet(1), namecoin-util(1), namecoin-qt(1) — the whole friend group, go say hi 👑

And that's the page!! namecoin-tx v28.0.0, dated October 2024, and it was a manual page titled NAMECOIN-TX(1) the entire time. Slay, stay hydrated, and always hex-encode responsibly 💜🧚

📦 where this page comes from