1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
Return-Path: <cannon@cannon-ciota.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 76432F12
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jan 2018 01:43:42 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from forward2.bravehost.com (forward2.bravehost.com [65.39.211.66])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B71001C0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jan 2018 01:43:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at bravehost.com
Received: from [10.137.3.35] (tor-exit1-readme.dfri.se [171.25.193.77])
(Authenticated sender: cannon@cannon-ciota.info)
by forward2.bravehost.com (Postfix) with ESMTPSA id 7854510F4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 29 Jan 2018 17:43:36 -0800 (PST)
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
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 30 Jan 2018 03:07:32 +0000
Subject: Re: [bitcoin-dev] NIST 8202 Blockchain Technology Overview
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jan 2018 01:43:42 -0000
-------- 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.
|
