Delivery-date: Mon, 17 Jun 2024 15:25:17 -0700
Sender: bitcoindev@googlegroups.com
Date: Mon, 17 Jun 2024 15:15:52 -0700 (PDT)
From: Eric Voskuil <eric@voskuil.org>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <72e83c31-408f-4c13-bff5-bf0789302e23n@googlegroups.com>
In-Reply-To: <gnM89sIQ7MhDgI62JciQEGy63DassEv7YZAMhj0IEuIo0EdnafykF6RH4OqjTTHIHsIoZvC2MnTUzJI7EfET4o-UQoD-XAQRDcct994VarE=@protonmail.com>
References: <gnM89sIQ7MhDgI62JciQEGy63DassEv7YZAMhj0IEuIo0EdnafykF6RH4OqjTTHIHsIoZvC2MnTUzJI7EfET4o-UQoD-XAQRDcct994VarE=@protonmail.com>
Subject: [bitcoindev] Re: Great Consensus Cleanup Revival
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_15648_368106650.1718662552445"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_15648_368106650.1718662552445
Content-Type: multipart/alternative; 
	boundary="----=_Part_15649_335122652.1718662552445"

------=_Part_15649_335122652.1718662552445
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Antoine,

Regarding potential malleability pertaining to blocks with only 64 byte=20
transactions, why is not a deserialization phase check for the coinbase=20
input as a null point not sufficient mitigation (computational=20
infeasibility) for any implementation that desires to perform permanent=20
invalidity marking?

Best,
Eric

ref: Weaknesses in Bitcoin=E2=80=99s Merkle Root Construction=20
<https://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/201902=
25/a27d8837/attachment-0001.pdf>

--=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 on the web visit https://groups.google.com/d/msgid/=
bitcoindev/72e83c31-408f-4c13-bff5-bf0789302e23n%40googlegroups.com.

------=_Part_15649_335122652.1718662552445
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Antoine,<br /><br />Regarding potential malleability pertaining to block=
s with only 64 byte transactions, why is not a deserialization phase check =
for the coinbase input as a null point not sufficient mitigation (computati=
onal infeasibility) for any implementation that desires to perform permanen=
t invalidity marking?<br /><br />Best,<br />Eric<div><br /></div><div>ref:=
=C2=A0<a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/at=
tachments/20190225/a27d8837/attachment-0001.pdf">Weaknesses in Bitcoin=E2=
=80=99s Merkle Root Construction</a><br /></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/72e83c31-408f-4c13-bff5-bf0789302e23n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/72e83c31-408f-4c13-bff5-bf0789302e23n%40googlegroups.com</a>.=
<br />

------=_Part_15649_335122652.1718662552445--

------=_Part_15648_368106650.1718662552445--