path: root/40/57d382c26c3a57bcfaf1270c423c1039e150e6

Delivery-date: Fri, 28 Mar 2025 17:03:08 -0700
Received: from mail-ot1-f59.google.com ([209.85.210.59])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBC5P5KEHZQLBBMXRTS7QMGQE25ANYYQ@googlegroups.com>)
	id 1tyJfH-00064u-Fe
	for bitcoindev@gnusha.org; Fri, 28 Mar 2025 17:03:08 -0700
Received: by mail-ot1-f59.google.com with SMTP id 46e09a7af769-72bc266dc24sf2909291a34.2
        for <bitcoindev@gnusha.org>; Fri, 28 Mar 2025 17:03:07 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1743206582; cv=pass;
        d=google.com; s=arc-20240605;
        b=h8y/wjLEXtZMI/yNNG6AukV1FrN21uuvzJm46uBFoPW/X0s6NDlexluo8AMka1E+6Q
         /7Zc/uM/UVuDxgrpV2XTCPDcEbnirvyA8ycbLcjBBosid690+8u8HBD+cYH1/EIyT8o9
         WTynXUKTZ/O8IZh1U8ary7ecWawKTWfAF9plPt8AzEHgqtJHYepMS5hQrylj0a6FYpRU
         aDLI3dA2KM7qnkusaYCZAlvW7/bZkSGrsN10Ay94kD1vbln8ZmqiDeO3sFs1AP+4LSLD
         Nm/UNLQX9I6fYs63tPNFs17nF8c3w/B5Rw1mLUl5kCuHX6a6Nzdz6BNBvA8VRgGwh55E
         pUEg==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:content-language:thread-index
         :content-transfer-encoding:mime-version:message-id:date:subject
         :in-reply-to:references:to:from:sender:dkim-signature;
        bh=+DYW8LmmNjPnEjCGKiHaJ7a5Vu2nJeE1NpGL42wc77k=;
        fh=ie7/V8OEFY/Emspe44tW+nQJtFfKOQlR+cFryjqD1EU=;
        b=YqikzRNRlgUtMgTW6USdwtnd8MLdH6s175AMB6602s3KpTyL86Wlm+9pjPoHDrE+i0
         KcbFUPEEclf259ex9ODisOVFM5B3VwnXKlVH+Sh9jYALxZp+FlpY8NBoZc7NoJkNbPbd
         G8NpIoNTeehft5IqUkTJs6bDOatyhNhgUWBhsyoHA/hK43L+vA9cCKgLpHoiy+ag/ZXN
         w8XvkCk2+Z85GE/4XA/qz4/EMRJ62JuV/CqFi89lO4iuRkUr/eiLOFOCWIG/cMkgjxVm
         GUqZ5fpPgSiQbevBmqS0DeqFEiO6aBG6/3NzD16fXNp1nvM7NrG8K2SjC4jG00ZTsxDw
         FsPA==;
        darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
       dkim=pass header.i=@voskuil-org.20230601.gappssmtp.com header.s=20230601 header.b=nfSseajU;
       spf=none (google.com: eric@voskuil.org does not designate permitted sender hosts) smtp.mailfrom=eric@voskuil.org;
       dara=pass header.i=@googlegroups.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1743206582; x=1743811382; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:content-language:thread-index
         :content-transfer-encoding:mime-version:message-id:date:subject
         :in-reply-to:references:to:from:sender:from:to:cc:subject:date
         :message-id:reply-to;
        bh=+DYW8LmmNjPnEjCGKiHaJ7a5Vu2nJeE1NpGL42wc77k=;
        b=gTfAvHHxKpEEBmMQOmqPgyhi3Kc2Bz3/yZboq5Cv1ISkHu96OejgDSaoTNlmMTlUPc
         1/PJUfbm41rmYfJjLLlYLnNTCXwy9huV4coX4pPaKHShQkezrLztYT9OfmuGWb5nVfMS
         M3nLh8DiA9l6LFGW5SLq9C9Ks66yW+QWbPprk4fUR329zmLP697EP9pdM2LJ/690eDc8
         FtpsIV31ShOHuTzkAkyCGjLmsJwE6QQkN/2KQyt36J3/eZGxm4AjhWZdNEEF9xk5aoZ2
         PPEJgcEGAdCyke/gQi1RNAHnhR3QFcOw2zER0tmfL3ye/gHNpK6EPXOIaDE994z3ZBCp
         fekA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1743206582; x=1743811382;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:content-language:thread-index
         :content-transfer-encoding:mime-version:message-id:date:subject
         :in-reply-to:references:to:from:x-beenthere:x-gm-message-state
         :sender:from:to:cc:subject:date:message-id:reply-to;
        bh=+DYW8LmmNjPnEjCGKiHaJ7a5Vu2nJeE1NpGL42wc77k=;
        b=hxL/U84et0L6/+SAhWhnkfuSazTeWiTa+JodtHZQJjcO5hTcAnRDyq763znmeqtMv/
         RiXGGnSlCqXkfEYHeKYI+c4f+KLMSnkeT2fsmJuvDfouJmtqLIikTky+yRxQ2rVIYrli
         qFM51W9dZo12NgeM1nsfJjBzRwur/Cj4QEtqTvqDKQ2GTqYddt23ZFr5s5RGyVHZFSLF
         yqyB9BxWzuppTwRM2xxZfMms1NPQTBZBl+A0F1dKaBbvQMNcbvnVXq2Kg/CR+1dn2h6J
         gkMEFPeem1O3+5l2D+zh7ICpu5SwwtGiors8OxjKWoYw8r/TIKgDHhvYEJ68X5VW9ZjH
         Gfew==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCWl++45pGHG9shxl1fUHCwnetPTVqbaw7vwL+TRxa+9Uk+CAyhhm/96hzQ3ymJ/0HhJ6Sk7QHeeJY8j@gnusha.org
X-Gm-Message-State: AOJu0YxQCOkqG/P7QtQx2Xxf4GhqPH2FYY0jtRINUpF9YX3rAebfcE9y
	wx3KRXoUQR4GSIp2pLCsQm839YRVDfrpZ74WjoHNCUEWVpNmRHTk
X-Google-Smtp-Source: AGHT+IGOfTUAvqLVd9g1sutljU2CSvqFol2FiUVubdXTcFmdbK9Ds+UP/SWfk6+mUPHMjKzet7dxXg==
X-Received: by 2002:a05:6830:304e:b0:72b:8363:d4f4 with SMTP id 46e09a7af769-72c6377d8d5mr835967a34.6.1743206581742;
        Fri, 28 Mar 2025 17:03:01 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=ARLLPAI1OC7lbuaAsUimCKwID6h0TxNErVDWUVuQVRjMZmkGiA==
Received: by 2002:a4a:b1c4:0:b0:601:afcc:166b with SMTP id 006d021491bc7-60278f82079ls1031404eaf.1.-pod-prod-09-us;
 Fri, 28 Mar 2025 17:02:58 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCUFxfCdrFLvNtL0Ozp5H+j4uK4+LmxawH98VqgvhEfzrnEOBJWu6rqGYFTQHkrSyqdLHxAFIvGarjNh@googlegroups.com
X-Received: by 2002:a05:6808:1302:b0:3fa:f848:8dfa with SMTP id 5614622812f47-3ff0f5a59abmr868349b6e.30.1743206578289;
        Fri, 28 Mar 2025 17:02:58 -0700 (PDT)
Received: by 2002:a05:6808:1aa6:b0:3f9:f009:458e with SMTP id 5614622812f47-3feefa6b8b7msb6e;
        Fri, 28 Mar 2025 12:53:55 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCUsyaawQY+FhFmaW58XSP/2AQqrXIpzDB+hOCpsacL2fRTQ/FTzRGWg+pu7/SGE0GDrFSGI96j/GwIP@googlegroups.com
X-Received: by 2002:a05:6830:6c0e:b0:727:28a:1ca5 with SMTP id 46e09a7af769-72c637c6390mr526318a34.16.1743191634940;
        Fri, 28 Mar 2025 12:53:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1743191634; cv=none;
        d=google.com; s=arc-20240605;
        b=NLSYJqd+eDENVEywVKnh/pZwozql4rlFcVWJ+RyDPqNGorVLlTSwArUI450lgLQXPY
         eKkQo5mi4LY6yT49M+3wH5jjXtyQomQYVwTB9WlXFB5Nfx+KJ63lE08Jmsj6BoyRsLIS
         +5gIyq17ZfkBUHtF2kUXwg2stsL85qHiXLRKZwlFaT9l3Ue4QSXbqcvq4smikObl0tqU
         y82QVFBILGqFPaMeYj353OCFcW1lZqDyFFp7F0+OcqTzEpyzOnysBVCoKCnRhwMhPQgB
         HaWtHfYBIw5mQq6utpgSGLKI6YWj9UN97Wsxcu4do31zrWRQDc7fQNqpngtfUB2RsxAW
         35cA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=content-language:thread-index:content-transfer-encoding
         :mime-version:message-id:date:subject:in-reply-to:references:to:from
         :dkim-signature;
        bh=MFr/bS9fdzNJjiUt3u2kr+hpjHV636xZdZKNL2/I6C4=;
        fh=Y/j/P4p2NsbE0WctKYOzqGnoLmJQXKktfYeAhW9Ix7w=;
        b=OJr/Ixn5dnAklZOediRaoaAFfcpHUy7T59hE0aAaJ9ByFJ4rAID8YJ98Oum3/ONR2S
         Qcim6iuAa5nwXYNgevlGK24P+VL3wC0/HvunnOgFjODo2MgtT+NRBVm0zMVrt5L5ED+g
         XGeLtiw0cg31ywl6Nazb5Cj9TfZsbwC2hEP/WEaNGUgkFLzo3Pc6gg3crIKCnS5owci0
         YX9utT9X7u86281zWxcf2B9PqfL0v9LPlcb7zR73sr3GGw10HEbfL5Yq6AnGcCN/t38U
         IBvrHx+4ok1hiR6peWCs5i1fjQu4qabhmjL5Qt70OeBYdDAJuJydipsJT+hlpBq4YIzq
         CeUg==;
        dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       dkim=pass header.i=@voskuil-org.20230601.gappssmtp.com header.s=20230601 header.b=nfSseajU;
       spf=none (google.com: eric@voskuil.org does not designate permitted sender hosts) smtp.mailfrom=eric@voskuil.org;
       dara=pass header.i=@googlegroups.com
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com. [2607:f8b0:4864:20::f29])
        by gmr-mx.google.com with ESMTPS id 46e09a7af769-72c58153046si128409a34.4.2025.03.28.12.53.54
        for <bitcoindev@googlegroups.com>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Fri, 28 Mar 2025 12:53:54 -0700 (PDT)
Received-SPF: none (google.com: eric@voskuil.org does not designate permitted sender hosts) client-ip=2607:f8b0:4864:20::f29;
Received: by mail-qv1-xf29.google.com with SMTP id 6a1803df08f44-6eeb7589db4so21993106d6.1
        for <bitcoindev@googlegroups.com>; Fri, 28 Mar 2025 12:53:54 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCV8fi8J4S71Y23XbGOrBUP6IuOwRzD3dzqUwHN6Cwy/xZyQ/CJxzmt/DqyOVUAOh2XHIdMBrwNInspo@googlegroups.com
X-Gm-Gg: ASbGncuDY0X2z1WLPeUH4VXZvghT00mXJRg4ZCbtoqF9ageb7rTBccfdAv53uAEYpL3
	x4lSV0zdduAQMNo/gU86XYNjjvEM5L3wefdscKo5ydwiMduNSI9bbSViyZmf12tgDCzHI2Rn0i7
	g78VT3jhwdSIdLX4OKdn7+Ta3fymM/KVamid70QM+yKjTxzmqmGyRlD1QSe4L4YgjFqai3ozYzE
	GKq0XSFKRc9wTCLRHSJPwJ5+JsyiRCYB1tQ4YvTcE6xL6mkJaS5KYCb/iWq0fFDnW9P+gGIriBG
	qzgmz/yZuTfKVu7jJRtBzkOyAHsFuwaWGc4tZU+zC3vPT8wUhcNedtGsf9cyEBitgauS0uaFct8
	3xwduA+C8vA==
X-Received: by 2002:a05:6214:d07:b0:6e8:e8dd:30d1 with SMTP id 6a1803df08f44-6eed623f69cmr4653636d6.22.1743191633776;
        Fri, 28 Mar 2025 12:53:53 -0700 (PDT)
Received: from ERICDESKTOP (c-73-227-67-43.hsd1.nh.comcast.net. [73.227.67.43])
        by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6eec9627b36sm14826406d6.6.2025.03.28.12.53.53
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 28 Mar 2025 12:53:53 -0700 (PDT)
From: <eric@voskuil.org>
To: "'jeremy'" <jeremy.l.rubin@gmail.com>,
	"'Bitcoin Development Mailing List'" <bitcoindev@googlegroups.com>
References: <uDAujRxk4oWnEGYX9lBD3e0V7a4V4Pd-c4-2QVybSZNcfJj5a6IbO6fCM_xEQEpBvQeOT8eIi1r91iKFIveeLIxfNMzDys77HUcbl7Zne4g=@protonmail.com> <CAGL6+mFQqTS21cQZ_aU=hXtMaKkw5ygAk2PT9hQpdB4THz9X_A@mail.gmail.com> <TD8gP8PKw3th-0DrZznBXrXFILRkwr66wVRoiPC2di_e-NivCRKVjooVZIh7JJSV_C9rJEkKTvudWSG8CJsq16jPhQBjM0eVmPe8rir50Y4=@protonmail.com> <afedbc69-8042-4fe8-99c2-279173a440f3n@googlegroups.com>
In-Reply-To: <afedbc69-8042-4fe8-99c2-279173a440f3n@googlegroups.com>
Subject: RE: [bitcoindev] Consensus Cleanup BIP draft
Date: Fri, 28 Mar 2025 15:53:51 -0400
Message-ID: <065901dba01b$2164fff0$642effd0$@voskuil.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHWtHeW1eEx0HT2gtpWV+YJenkSdAJggGU8AIKIJN0B5cf6jLNsgZQQ
Content-Language: en-us
X-Original-Sender: eric@voskuil.org
X-Original-Authentication-Results: gmr-mx.google.com;       dkim=pass
 header.i=@voskuil-org.20230601.gappssmtp.com header.s=20230601
 header.b=nfSseajU;       spf=none (google.com: eric@voskuil.org does not
 designate permitted sender hosts) smtp.mailfrom=eric@voskuil.org;
       dara=pass header.i=@googlegroups.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)

Hi Jeremy,

> I'm also personally strongly against removing 64-byte transactions. It's =
a wart
> in how transactions work, and future upgrades (especially around tx
> programmability) might integrate very poorly with this kind of edge condi=
tion.

I tend to agree. This kind of discontinuity always comes back to bite event=
ually. That concern should not be dismissed so casually.

But more to the point, it does not solve any of the problems that were orig=
inally provided as justification, apart from making it slightly simpler to =
implement an SPV wallet (no need to get the coinbase tx). This was discusse=
d at very great length here and on delving by myself and others, and I beli=
eve that it was fully accepted that the only justification is this SPV ques=
tion. There are no issues of security or performance for any code, and not =
even a code simplification for a node. It's a new consensus rule that creat=
es this discontinuity - only to make an SPV wallet very slightly easier to =
implement. There is no other benefit whatsoever. I want to emphasize this b=
ecause in the discussion it still seems that people may be holding on to th=
e idea that it provides some other benefit - it doesn't. If people agree th=
at this is a worthwhile trade, I'm not going to lose any sleep over it. But=
 I don't like seeing arguments about consensus being based on implementatio=
n details - especially when they are flawed. It feels very much to me that =
this is what got this issue going (the several rejected arguments about nod=
e performance and simplification), and may be in part what's still driving =
it.

I ACK the single activation concept, but don't accept that a rule should be=
 deployed that would not stand on its own justification.

Also, I do appreciate the work that Antoine and others have done on the set=
 of issues overall.

Best,
Eric

> On Thursday, March 27, 2025 at 3:36:13=E2=80=AFPM UTC-4 Antoine Poinsot w=
rote:
>=20
>=20
> 	Hi Chris,
>=20
> 	As i already explained on this very list 2 months ago [0], i don't find
> the argument for splitting my BIP convincing. On the contrary i think it =
would
> be counterproductive as it would create more churn, invite bikeshedding a=
nd
> overall impede progress on this proposal.
>=20
>=20
> 		we've successfully activated multiple BIPs within a single soft
> fork in the past=E2=80=94e.g., BIP141 and BIP143 in Segwit, as well as BI=
P341,
> BIP342, and BIP343 in Taproot.
>=20
>=20
>=20
> 	Those BIPs had much more content to them. The specifications of the
> Consensus Cleanup is trivial in comparison: they fit in less than a dozen=
 lines of
> text when described in details. Splitting them in 4 different BIPs with a=
 single or
> a couple lines of specifications would just introduce unnecessary overhea=
d.
>=20
>=20
> 		if one of the proposed changes turns out to be controversial,
> we could remove it without holding up the rest of the improvements.
>=20
>=20
>=20
> 	First of all, i do not expect to remove any of the mitigations from the
> BIP at this stage. The fact that each of these mitigations was researched=
 and
> discussed at length by multiple people over the past year gives me confid=
ence
> to move forward with every single one of those. Otherwise i would not hav=
e
> proposed this BIP in the first place.
>=20
> 	Now, even if somehow we should drop one of the mitigations from
> the proposal, having them in separate BIPs does not make that any easier.
>=20
>=20
> 		More active contributors to the project may have stronger
> opinions on the best approach there.
>=20
>=20
>=20
> 	Yes.
>=20
> 	Best,
> 	Antoine
>=20
>=20
> 	[0]
> https://gnusha.org/pi/bitcoindev/mm_NvE4votqtjm455I3AmdrLOTzwgfFpq
> btbFFNy0Zf2PywGt220MXfn76it60q_kbnS9Rw97cv6XzqogNgQMfIXi6-
> HdOnamw7tUrMtmXc=3D@protonmail.com
>=20
> 	On Thursday, March 27th, 2025 at 6:46 AM, Chris Stewart
> <stewart....@gmail.com> wrote:
>=20
>=20
> 		Hi Antoine,
>=20
> 		First off, concept ACK. My concerns are procedural rather than
> objections to the individual security fixes themselves.
>=20
> 		The "Great Consensus Cleanup" is a fantastic brand for
> communicating these protocol changes to non-technical users. However, sin=
ce
> this is a technical forum and we are producing BIPs intended for technica=
l
> audiences, I believe we should document these changes in separate BIPs.
>=20
> 		The proposed security fixes are largely unrelated from a
> technical standpoint:
>=20
> 		1.	Timewarp attack mitigation
>=20
> 		2.	Worst-case block validation constraints
>=20
> 		3.	Disallowing 64-byte transactions
>=20
> 		4.	Avoiding duplicate transactions
>=20
> 		We should absolutely retain the "Great Consensus Cleanup"
> branding while independently documenting each security enhancement.
>=20
> 		A common concern I=E2=80=99ve heard about splitting this BIP is that
> deploying soft forks is difficult, so all changes should be bundled toget=
her.
> While soft fork deployment is indeed challenging, we've successfully acti=
vated
> multiple BIPs within a single soft fork in the past=E2=80=94e.g., BIP141 =
and BIP143 in
> Segwit, as well as BIP341, BIP342, and BIP343 in Taproot. If the communit=
y
> reaches consensus, we can still deploy all these changes together, even i=
f they
> are documented separately.
>=20
> 		This approach also provides flexibility: if one of the proposed
> changes turns out to be controversial, we could remove it without holding=
 up
> the rest of the improvements. Additionally, once these fixes are deployed=
,
> there will likely be significant research and documentation to incorporat=
e, and
> maintaining independent BIPs will make it easier to manage that growth.
>=20
> 		I do see merit in implementing all the security fixes in a single
> PR for Bitcoin Core. More active contributors to the project may have str=
onger
> opinions on the best approach there.
>=20
>=20
>=20
> 		-Chris
>=20
>=20
> ________________________________
>=20
>=20
>=20
>=20
>=20
> 		On Wed, Mar 26, 2025 at 1:23=E2=80=AFPM 'Antoine Poinsot' via
> Bitcoin Development Mailing List <bitco...@googlegroups.com> wrote:
>=20
>=20
> 			Hi everyone,
>=20
> 			About two months ago i shared an update on this list
> about my (and others', really) work on the
> 			Consensus Cleanup [0]. I am now ready to share a BIP
> draft for a Consensus Cleanup soft fork.
>=20
> 			The BIP draft can be found here:
> https://github.com/darosior/bips/blob/consensus_cleanup/bip-cc.md
>=20
> 			It includes the following fixes:
> 			- a restriction on the timestamp of the first and last
> blocks of a difficulty adjustment period to
> 			address the Timewarp and Murch-Zawy attacks;
> 			- a limit on the number of legacy signature operations
> that may be executed in validating a single
> 			transaction to address long block validation times;
> 			- making 64 bytes transactions invalid to address
> weaknesses in the block Merkle tree construction;
> 			- mandating coinbase transactions be timelocked to
> their block height to prevent future transaction
> 			duplication without resorting to BIP30 validation.
>=20
> 			This BIP draws on the 2019 Great Consensus Cleanup
> proposal from Matt Corallo [1]. A number of
> 			people contributed ideas, testing, data or useful
> discussions. This includes Ava Chow, Matt Corallo,
> 			Mark Erhardt, Brian Groll, David A. Harding, Sjors
> Provoost, Anthony Towns, Greg Sanders, Chris
> 			Stewart, Eric Voskuil, @0xb10c and others.
>=20
> 			Antoine Poinsot
>=20
> 			[0]
> https://gnusha.org/pi/bitcoindev/jiyMlvTX8BnG71f75SqChQZxyhZDQ65kldc
> ugeIDJVJsvK4hadCO3GT46xFc7_cUlWdmOCG0B_WIz0HAO5ZugqYTuX5qxnN
> LRBn3MopuATI=3D@protonmail.com
> 			[1]
> https://github.com/TheBlueMatt/bips/blob/7f9670b643b7c943a0cc6d2197
> d3eabe661050c2/bip-XXXX.mediawiki
>=20
> 			--
> 			You received this message because you are subscribed
> to the Google Groups "Bitcoin Development Mailing List" group.
> 			To unsubscribe from this group and stop receiving
> emails from it, send an email to bitcoindev+...@googlegroups.com.
> 			To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/uDAujRxk4oWnEGYX9lBD3e
> 0V7a4V4Pd-c4-
> 2QVybSZNcfJj5a6IbO6fCM_xEQEpBvQeOT8eIi1r91iKFIveeLIxfNMzDys77HUc
> bl7Zne4g%3D%40protonmail.com.
>=20
>=20
>=20
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups.com
> <mailto:bitcoindev+unsubscribe@googlegroups.com> .
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/afedbc69-8042-4fe8-99c2-
> 279173a440f3n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/afedbc69-8042-4fe8-99c2-
> 279173a440f3n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfo
> oter> .


--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
065901dba01b%242164fff0%24642effd0%24%40voskuil.org.