-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Pardon my unproffesional tone in my original comment.
But thank you for passing on these corrections. This looks much better.
I have a few comments that might lend to making this even more accurate or
complete.
It is nice to see Bitcoin Cash use the
Williamson; Bitcoin Protocol Discussion
Subject: Re: [bitcoin-dev] NIST 8202 Blockchain Technology Overview
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/31/2018 11:16 AM, Damian Williamson wrote:
> I disagree with the correctness of the following statement:
>
>
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/31/2018 11:16 AM, Damian Williamson wrote:
> I disagree with the correctness of the following statement:
>
>
>> Rather than implementing the SegWit changes, the developers of Bitcoin Cash
>> decided to simply increase the blocksize.
>
>
>
On Tue, Jan 30, 2018 at 03:30:21AM +, CANNON via bitcoin-dev wrote:
> On 01/30/2018 01:43 AM, CANNON via bitcoin-dev wrote:
> >
> >
> > Forwarded Message
> > Subject: RE: NIST 8202 Blockchain Technology Overview
> > Date: Mon, 29 Jan 2018 12:25:05 +
> > From: Yaga, Dylan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/30/2018 01:43 AM, CANNON via bitcoin-dev wrote:
>
>
> Forwarded Message
> Subject: RE: NIST 8202 Blockchain Technology Overview
> Date: Mon, 29 Jan 2018 12:25:05 +
> From: Yaga, Dylan (Fed)
> To: CANNON
>
> Thank you
Forwarded Message
Subject: RE: NIST 8202 Blockchain Technology Overview
Date: Mon, 29 Jan 2018 12:25:05 +
From: Yaga, Dylan (Fed)
To: CANNON
Thank you for your comments.
You, along with many others, expressed concern on section 8.1.2.
To help foster a full transparency ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Slight correction to email I just posted titled "NIST 8202 Blockchain
Technology Overview"
The date in top of email states Jan 20, corrected date is Jan 28th which can be
validated
also by verifying my signature (gpg includes timestamp when signing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
January 20 2018
(I am also forwarding this message to the bitcoin mailing list just in case
there
are other technological errors that could use correction in this draft paper or
anything that should be added with my comments.)
To the authors of th
