public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.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: Tue, 11 Apr 2023 14:27:27 +0200	[thread overview]
Message-ID: <CRTXCM2IHVCZ.3OICMAE871TH2@vincent-arch> (raw)
In-Reply-To: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one>

On Wed Apr 5, 2023 at 8:54 PM CEST, 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.

Make a lot of sense to me, just recently I found that 
I was using a complete different word to refering to `scriptPubKey` 
that only me was using :)

So, concept ACK.

Thanks!

Vincent.


  parent reply	other threads:[~2023-04-11 12:27 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 ` [bitcoin-dev] Seeking concept ACKs for transaction terminology BIP Murch
2023-04-05 22:05   ` Andrew Poelstra
2023-04-06  9:03   ` darosior
2023-04-11 12:27   ` Vincenzo Palazzo [this message]
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=CRTXCM2IHVCZ.3OICMAE871TH2@vincent-arch \
    --to=vincenzopalazzodev@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=murch@murch.one \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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