From: josibake <josibake@protonmail•com>
To: Murch <murch@murch•one>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Seeking concept ACKs for transaction terminology BIP
Date: Fri, 21 Apr 2023 09:36:08 +0000 [thread overview]
Message-ID: <a5C5saUWE_hqdhv-xjQmgXchsVpGg4Oe4fURovdPyGruniWlCz6JYZ8MZh1xVHL5ikpqSaoliMlKuEgLjVGE-O7rlJzaMPpYSAFawns33eo=@protonmail.com> (raw)
In-Reply-To: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one>
[-- Attachment #1.1: Type: text/plain, Size: 1862 bytes --]
Big Concept ACK.
I've participated in several Bitcoin developer education programs over the past few years and have noticed that a consistent stumbling block for students is reconciling the different terms used in blogs, transcripts, mailing list posts, etc.
Having a reference document like this to include early in the curriculum(s) will help reduce cognitive load.
In particular, I'd like to highlight the importance of the "synonyms" field: since we can't retroactively re-write materials using different terms, having the synonyms will help map various resources to a shared terminology.
Thanks for working on this!
Cheers,
Josie
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, April 5th, 2023 at 8:54 PM, 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—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 #1.2: publickey - josibake@protonmail.com - 0x616516B8.asc --]
[-- Type: application/pgp-keys, Size: 3154 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
next prev parent reply other threads:[~2023-04-21 9:36 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
2023-04-11 12:27 ` Vincenzo Palazzo
2023-04-21 9:36 ` josibake [this message]
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='a5C5saUWE_hqdhv-xjQmgXchsVpGg4Oe4fURovdPyGruniWlCz6JYZ8MZh1xVHL5ikpqSaoliMlKuEgLjVGE-O7rlJzaMPpYSAFawns33eo=@protonmail.com' \
--to=josibake@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