From: Murch <murch@murch•one>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Seeking concept ACKs for transaction terminology BIP
Date: Wed, 5 Apr 2023 14:54:15 -0400 [thread overview]
Message-ID: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one> (raw)
In-Reply-To: <e2293b77-aef3-62cf-01e3-d89a7beb8e8c@murch.one>
Hey everyone,
Over the years, I have participated in a few conversations about various
aspects of transactions. Often a chunk of the conversation is spent on
establishing a shared vocabulary. There are many competing terms—e.g. I
can think of at least three additional terms that refer to `scriptPubKey`.
I’ve drafted an informational BIP that proposes terminology for various
components and aspects of transactions. As some established terms are
already contradictory, the proposal does not aim for a perfectly
consistent selection of terms, but rather just to establish a shared
vocabulary to avoid confusion.
Draft: https://github.com/Xekyo/bips/pull/1
Please let me know whether you’d be interested in the creation of such a
BIP.
Cheers,
Murch
next parent reply other threads:[~2023-04-05 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2293b77-aef3-62cf-01e3-d89a7beb8e8c@murch.one>
2023-04-05 18:54 ` Murch [this message]
2023-04-05 22:05 ` Andrew Poelstra
2023-04-06 9:03 ` darosior
2023-04-11 12:27 ` Vincenzo Palazzo
2023-04-21 9:36 ` josibake
2023-05-10 20:20 ` Keagan McClelland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one \
--to=murch@murch$(echo .)one \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox