📅 Original date posted:2017-04-06
📝 Original message:Can you please not forget to supply us more details on the claims made
regarding the reverse engineering of the Asic chip?
It is absolutely crucial that we get these independently verified ASAP.
Daniele
Message: 2
> Date: Thu, 6 Apr 2017 21:38:31 +0000
> From: Gregory Maxwell <greg at xiph.org>
> To: Bitcoin Dev <bitcoin-dev at lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on
> the Bitcoin POW function
> Message-ID:
> <CAAS2fgSTrMjKZVpL4wRidnzTCC9O3OEF=oCnROf1pggz2cDgJA at mail.
> gmail.com>
> Content-Type: text/plain; charset=UTF-8
> On Wed, Apr 5, 2017 at 9:37 PM, Gregory Maxwell <greg at xiph.org> wrote:
> > each block MUST either contain a BIP-141 segwit commitment or a
> > correct WTXID commitment with ID 0xaa21a9ef.
> It was just pointed out to me that the proposed ID (which I just
> selected to be above the segwit one) collides with one chosen in
> another non-BIP proposal. This wasn't intentional, and I'll happily
> change the value when I update the document.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170407/6fcc62db/attachment.html>;
Daniele Pinna [ARCHIVE] /
npub16z…jg59c
2023-06-07 17:59:28
in reply to nevent1q…euq9
Author Public Key
npub16z2msvydkmd6xsjyrggnavcwrlpevfwq74x5avxrkg2dpq7cg6js5jg59cPublished at
2023-06-07 17:59:28Event JSON
{
"id": "c1c4a8f16a4ea0ea53920a7f60bd3bb8722d8ca19a9e2cc6bae9499607744937",
"pubkey": "d095b8308db6dba342441a113eb30e1fc39625c0f54d4eb0c3b214d083d846a5",
"created_at": 1686160768,
"kind": 1,
"tags": [
[
"e",
"ad36e2a7543163ffef3218fa3d55149ec67fbe14dd109a89d2940c12712bdc10",
"",
"root"
],
[
"e",
"5bbfe3609df824732e6b34e1d20c763282e820b427ea0822a730c865db5b28fe",
"",
"reply"
],
[
"p",
"6b8e77368804013d7126ba4b77c7963bcfeff909135791531097d7a0f03ca85d"
]
],
"content": "📅 Original date posted:2017-04-06\n📝 Original message:Can you please not forget to supply us more details on the claims made\nregarding the reverse engineering of the Asic chip?\n\nIt is absolutely crucial that we get these independently verified ASAP.\n\nDaniele\n\nMessage: 2\n\u003e Date: Thu, 6 Apr 2017 21:38:31 +0000\n\u003e From: Gregory Maxwell \u003cgreg at xiph.org\u003e\n\u003e To: Bitcoin Dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e Subject: Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on\n\u003e the Bitcoin POW function\n\u003e Message-ID:\n\u003e \u003cCAAS2fgSTrMjKZVpL4wRidnzTCC9O3OEF=oCnROf1pggz2cDgJA at mail.\n\u003e gmail.com\u003e\n\u003e Content-Type: text/plain; charset=UTF-8\n\u003e On Wed, Apr 5, 2017 at 9:37 PM, Gregory Maxwell \u003cgreg at xiph.org\u003e wrote:\n\u003e \u003e each block MUST either contain a BIP-141 segwit commitment or a\n\u003e \u003e correct WTXID commitment with ID 0xaa21a9ef.\n\u003e It was just pointed out to me that the proposed ID (which I just\n\u003e selected to be above the segwit one) collides with one chosen in\n\u003e another non-BIP proposal. This wasn't intentional, and I'll happily\n\u003e change the value when I update the document.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170407/6fcc62db/attachment.html\u003e",
"sig": "d61979b2c80b6b802d1ec4437b330d74d41e25ef08b9d67e07fd789f33aedc147ffb151e1b5c710155062777bbdbcb7d7ea70cb94e248e2314bfb1773d9a1377"
}