From: darosior <darosior@protonmail•com>
To: murch@murch•one, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Seeking concept ACKs for transaction terminology BIP
Date: Thu, 06 Apr 2023 09:03:14 +0000 [thread overview]
Message-ID: <2XsUsUI5897rVs5yUk4ZouSNyEukPZzy6hmUYxtNM2s-MBkoucqFfHRWbjiaIPIZwDhhwcIXdmGNYLZnzWyhjSpNOn4VB-EgifLU5HmUHY0=@protonmail.com> (raw)
In-Reply-To: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hello Murch,
It makes sense to me too. Thanks!
Antoine
-------- Original Message --------
On Apr 5, 2023, 8:54 PM, Murch via bitcoin-dev wrote:
> 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 _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists•linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 1311 bytes --]
next prev parent reply other threads:[~2023-04-06 9:03 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
2023-04-05 22:05 ` Andrew Poelstra
2023-04-06 9:03 ` darosior [this message]
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='2XsUsUI5897rVs5yUk4ZouSNyEukPZzy6hmUYxtNM2s-MBkoucqFfHRWbjiaIPIZwDhhwcIXdmGNYLZnzWyhjSpNOn4VB-EgifLU5HmUHY0=@protonmail.com' \
--to=darosior@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=murch@murch$(echo .)one \
/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