MIME-Version: 1.0
References: <e2293b77-aef3-62cf-01e3-d89a7beb8e8c@murch.one>
 <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one>
In-Reply-To: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Wed, 10 May 2023 16:20:53 -0400
Message-ID: <CALeFGL0iXvdw2CFjDaAP5EtKf3eL31Vg0ejLF3USBBTPoeZrcA@mail.gmail.com>
To: Murch <murch@murch.one>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000007d25a405fb5c9c82"
Subject: Re: [bitcoin-dev] Seeking concept ACKs for transaction terminology
	BIP
Precedence: list

--0000000000007d25a405fb5c9c82
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Concept ACK,

The only way we can hope to have productive discussion is to minimize the
amount of effort spent in miscommunication especially that which arises
from unclear terminology. Which exact words refer to which meanings is
somewhat arbitrary, (look at math, particularly abstract math), but what
matters is that there is precision in their use to whatever degree is
possible. Having a document of shared terminology helps us communicate with
one another and speeds up the process of coming to social consensus on
issues.

Stay Inspired,
Keags

On Wed, Apr 5, 2023 at 2:54=E2=80=AFPM Murch via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> 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=E2=80=94=
e.g. I
> can think of at least three additional terms that refer to `scriptPubKey`=
.
>
> I=E2=80=99ve drafted an informational BIP that proposes terminology for v=
arious
> 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=E2=80=99d 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
>

--0000000000007d25a405fb5c9c82
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Concept ACK,<div><br></div><div>The only way we can hope t=
o have productive discussion is to minimize the amount of effort spent in m=
iscommunication especially that which arises from unclear terminology. Whic=
h exact words refer to which meanings is somewhat arbitrary, (look at math,=
 particularly abstract math), but what matters is that there is precision i=
n their use to whatever degree is possible. Having a document of shared ter=
minology helps us communicate with one another and speeds up the process of=
 coming to social consensus on issues.</div><div><br></div><div>Stay Inspir=
ed,</div><div>Keags</div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Wed, Apr 5, 2023 at 2:54=E2=80=AFPM Murch via b=
itcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bit=
coin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">Hey everyone,<br>
<br>
Over the years, I have participated in a few conversations about various <b=
r>
aspects of transactions. Often a chunk of the conversation is spent on <br>
establishing a shared vocabulary. There are many competing terms=E2=80=94e.=
g. I <br>
can think of at least three additional terms that refer to `scriptPubKey`.<=
br>
<br>
I=E2=80=99ve drafted an informational BIP that proposes terminology for var=
ious <br>
components and aspects of transactions. As some established terms are <br>
already contradictory, the proposal does not aim for a perfectly <br>
consistent selection of terms, but rather just to establish a shared <br>
vocabulary to avoid confusion.<br>
<br>
Draft: <a href=3D"https://github.com/Xekyo/bips/pull/1" rel=3D"noreferrer" =
target=3D"_blank">https://github.com/Xekyo/bips/pull/1</a><br>
<br>
Please let me know whether you=E2=80=99d be interested in the creation of s=
uch a <br>
BIP.<br>
<br>
Cheers,<br>
Murch<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000007d25a405fb5c9c82--