To: bitcoin-dev@lists.linuxfoundation.org
References: <6d24833d-f127-04ea-d180-c69409de16a5@cannon-ciota.info>
From: CANNON <cannon@cannon-ciota.info>
Message-ID: <6d92d8da-052d-f997-f441-0713acd72e85@cannon-ciota.info>
Date: Tue, 30 Jan 2018 01:43:22 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <6d24833d-f127-04ea-d180-c69409de16a5@cannon-ciota.info>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [bitcoin-dev] NIST 8202 Blockchain Technology Overview
Precedence: list


-------- Forwarded Message --------
Subject: RE: NIST 8202 Blockchain Technology Overview
Date: Mon, 29 Jan 2018 12:25:05 +0000
From: Yaga, Dylan (Fed) <dylan.yaga@nist.gov>
To: CANNON <cannon@cannon-ciota.info>

Thank you for your comments.
You, along with many others, expressed concern on section 8.1.2.
To help foster a full transparency approach on the editing of this section, I am sending the revised section to you for further comment. 

8.1.2	Bitcoin Cash (BCH)
In 2017, Bitcoin users adopted an improvement proposal for Segregated Witness (known as SegWit, where transactions are split into two segments: transactional data, and signature data) through a soft fork. SegWit made it possible to store transactional data in a more compact form while maintaining backwards compatibility.  However, a group of users had different opinions on how Bitcoin should evolve – and developed a hard fork of the Bitcoin blockchain titled Bitcoin Cash. Rather than implementing the SegWit changes, the developers of Bitcoin Cash decided to simply increase the blocksize. When the hard fork occurred, people had access to the same amount of coins on Bitcoin and Bitcoin Cash.