From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id B41D7C002A for ; Wed, 10 May 2023 20:21:08 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 5D3ED427C7 for ; Wed, 10 May 2023 20:21:08 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5D3ED427C7 Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20221208 header.b=PshQYiSH X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UmW2wR-ZoHT for ; Wed, 10 May 2023 20:21:07 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CC13341FD6 Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by smtp4.osuosl.org (Postfix) with ESMTPS id CC13341FD6 for ; Wed, 10 May 2023 20:21:06 +0000 (UTC) Received: by mail-wr1-x430.google.com with SMTP id ffacd0b85a97d-3077d134028so4330630f8f.3 for ; Wed, 10 May 2023 13:21:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683750065; x=1686342065; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=tmsLahZ72W2oxZ3zDvI1eeof8+46yekAddMZvmmjaQI=; b=PshQYiSHTwOMT6vlyXtgsdddutnxJ2y10njY40GQbHypbdbyUOG15HmCZIlQBA/9ZW DTxGhVFYh+uhSLIMOrvmlHsQHBuUvNJqK02AGbumrDNXPyIZGR/o37x0adzhRmenq9qw rm2CCqkeV/m9MnJU+hTUv38quWIpsspo1Nq7Rc53TIjxbj+tbg8HzVvYFnIRSy4kwf8s RxvKwVRPt29Q6z4ccQbbj5U7iF9Fau/JD3H5HRs1GLAWCuYxdd4quW/lVuJ2Q2biJOEH nHudBy1jBFYH+wX1rxSsH4ioxy7ob58NcyxMmKIuRYbWWyhuVEzj8H/ZcBwZmdh/vGeV yL1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683750065; x=1686342065; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=tmsLahZ72W2oxZ3zDvI1eeof8+46yekAddMZvmmjaQI=; b=GVdylGO3modUjPWNtTFO7ADUiTCn3Gl6AWiO+QYYgIjnlJeKfVJ7GE3GBEKioAuA5m CKwn0/PvftUJ0wyNviCdBKZcfs0lenbi1eGrEGix6iAlqvxWuM4aXrdfDGO+LufdvOqF rQJlnX9/ZlykZLKocCkBEqa3HQbLBJ2fVMon0s8j9BEl2v3zWFo635/maHlowt+8Az1X ofOhFOTutmt9Mlzl6kKRlW312HTWxSsQz3dfxoDhMuBNB5UC+hNXmrl8fGbqopCyVwWz 2M6dXkxj19wqsbV+RDtK7EuEVFvFiCZ+lA0/8cMMrNn5gXFXpggEzvV9enT8D+8zX0v9 c7Vg== X-Gm-Message-State: AC+VfDxmieMvFlaTZd5VDfnLXyrTRp6y1Ppo6iGl0uhy3tUT79N4Idvq kshSXsdRfR0b6hPaR+vaF7bskUAZvYDWb8MkbCQe4jRNnf0= X-Google-Smtp-Source: ACHHUZ7B8xg8ngL8gIMBkirtTG3mSZXcvE08IQ2bL2Hlvkzgz3HwPqAw+tXc3KDX6KSxEoAq0DItJYa19XcH3I1/0Mo= X-Received: by 2002:adf:e4c8:0:b0:304:8888:87ad with SMTP id v8-20020adfe4c8000000b00304888887admr14007898wrm.12.1683750064562; Wed, 10 May 2023 13:21:04 -0700 (PDT) MIME-Version: 1.0 References: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one> In-Reply-To: <6bb373cc-bee0-13a3-a510-b65d4faa867f@murch.one> From: Keagan McClelland Date: Wed, 10 May 2023 16:20:53 -0400 Message-ID: To: Murch , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000007d25a405fb5c9c82" X-Mailman-Approved-At: Thu, 11 May 2023 11:55:00 +0000 Subject: Re: [bitcoin-dev] Seeking concept ACKs for transaction terminology BIP X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2023 20:21:08 -0000 --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
Concept ACK,

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.

Stay Inspir= ed,
Keags

On Wed, Apr 5, 2023 at 2:54=E2=80=AFPM Murch via b= itcoin-dev <bit= coin-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=94e.= g. I
can think of at least three additional terms that refer to `scriptPubKey`.<= br>
I=E2=80=99ve drafted an informational BIP that proposes terminology for var= ious
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 s= uch a
BIP.

Cheers,
Murch
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--0000000000007d25a405fb5c9c82--