summaryrefslogtreecommitdiff
path: root/5f/770251640c30a9021ca2a1080eeae52bdeb778
blob: 4ae362e2d71d054a7f6346477c76b782663d8de0 (plain)
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
Return-Path: <li3939108@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 93FE9FF8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 17 Jan 2018 07:55:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com
	[209.85.128.172])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AFCDA14E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 17 Jan 2018 07:55:56 +0000 (UTC)
Received: by mail-wr0-f172.google.com with SMTP id t16so4224059wrc.10
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 16 Jan 2018 23:55:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:from:date:message-id:subject:to;
	bh=RbHZAtnPWNX/FO2tLOrcc1DY934qnPdv77z+rk1GAno=;
	b=DpJ05ICPqPp4vxF3ChdkC1TZnR7Gd4CaVnOnp+4j7duBEtgEsBqWmpXZss2ZUwEr0p
	E7ar9ujdTkYvtKqTj0F4qJKVqNpilCethnFKcAohBHrBP1cWSyxDtrhCa51PYFpAH09/
	5n9Fu5vsPoDH8LHUw2y8XAVLhhu8/6eDngNXe5YgvKw/xsU2Js3VOtFhHH+nSamXlVmE
	09UsbN0yPDioUTcxVyTVKR32EEsOE+W/iowQAqcyStY2cuJ/SeMd25IaJloemKLUHwUI
	khRgXb3VlLFI82DHHcAkYRWIN8sNrMwUdajGr+xBJAsAeQK2BigHBsX2rkMHrDZGF0Za
	xGaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=RbHZAtnPWNX/FO2tLOrcc1DY934qnPdv77z+rk1GAno=;
	b=rjBdTWB1Pxa4nGst6CsapGZvSBSmpQmgLp5rmQHRR74R8WAEa9GNAxbRL4FBcWnrCJ
	B2zN9HW4hskY22kHlJnJOE6uIVc2CCLxxEo7EHbAm7y2vLHwfG5T2uB6lrXqnVtmVP1K
	dNdhHdXQ7amSNAb9mSZIXlTyWUVbacLU5kiqF0Pi8b7zouBDjD/sAEKJZ7menN8wQ4lD
	g9dAX5ZoPorSPGxNwWFg0pHRbanf0nnM1T3CiAUZseqt+twHXVwDNKXMni+4teV3jtq1
	aQufQPLGInQY6MhWwcoYpkcLIPjUqpqjz80r/yYGEa8FUYofR2edAo+K6mrJO3yx+cKN
	XSFw==
X-Gm-Message-State: AKwxyteCCcnmOuoqfNgjc0Dj+P1dv+UA2Y7ontpQW1lga+v4hZtDN7Et
	OScdBQhQQxTNFAqAXhP6WhAswthvLHafhwMr57cm2w==
X-Google-Smtp-Source: ACJfBovSKxN+mv21r1sXVJAObWiigx+9tMyFZnfQZX/WADRKzf/PAl/ofe1NnHw5IaVgZR98shimF2CccBwlP3Kw5J0=
X-Received: by 10.223.128.98 with SMTP id 89mr1615893wrk.280.1516175755143;
	Tue, 16 Jan 2018 23:55:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.132.134 with HTTP; Tue, 16 Jan 2018 23:55:54 -0800 (PST)
From: Chaofan Li <li3939108@gmail.com>
Date: Wed, 17 Jan 2018 01:55:54 -0600
Message-ID: <CANZDnNomrpBTJU4=J1QqJpDePJ6RXyYsrwa=b9ZZOjyf1utQBw@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="94eb2c06a2ee4d6e5d0562f42dac"
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
	HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 17 Jan 2018 14:27:35 +0000
Subject: [bitcoin-dev] Blockchain Voluntary Fork (Split) Proposal
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: Wed, 17 Jan 2018 07:55:57 -0000

--94eb2c06a2ee4d6e5d0562f42dac
Content-Type: text/plain; charset="UTF-8"

Here I propose a simple method to solve the scalability issue of blockchain.
It is more like a financial trick rather than a technical solution.

The technical part is very simple:
Split ( hard fork ) the blockchain into two or more blockchains (e.g. two
blockchain A and B), voluntarily.
The two blockchains are the same except for some identifiers to distinguish
the two blockchains.
The coins on one blockchains cannot be sent to the other one or interfered
by the other blockchain (  considering so many hard forks in the last year,
the replay protection should work in this situation)
Everyone get double bitcoins. Each has half  value of original one bitcoin.
Then, we have two almost same blockchains and the capacity of the original
blockchain is doubled theoretically.
When sending coin, the wallet should select one blockchain randomly and try
to send through only  one blockchain (If there is enough bitcoins)
I think it is a  possible solution, if the community realize  no previously
owned asset value  is lost.

The method is inspired by the stock split
<https://en.wikipedia.org/wiki/Stock_split>.
When a stock share is split, for example into two shares, the price halves.
The market capitalization remains the same.
There is no dilution of every shareholders' total assets.

The bitcoin often emphasizes that the total coin supply should not be
changed.
If the total supply increases, the value of a single coin will be diluted.
That is true.
However, the bad part of inflation of fiat money is not  diluted value of
every unit of fiat money caused by total supply increase.
The problem is the increased supply is not delivered to everyone
proportional to their previously owned money.
The increased supply is released through debt expansion.
The people that can borrow more money with low interest ratio (during QE,
it was nearly 0) can invest  and get profit.
Or they don't even need to pay back the debt. The debt is left to
government, which might never pay back the debt, and some  get more money
from government.
Others' money are diluted.

With voluntary split of bitcoin, dilution of anyone's bitcoin assets won't
happen.

--94eb2c06a2ee4d6e5d0562f42dac
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div><br></div><div>Here I propose a simple=
 method to solve the scalability issue of blockchain.<br></div><div>It is m=
ore like a financial trick rather than a technical solution.=C2=A0</div><di=
v><br></div><div>The technical part is very simple:=C2=A0</div><div>Split (=
 hard fork ) the blockchain into two or more blockchains (e.g. two blockcha=
in A and B), voluntarily.=C2=A0</div><div>The two blockchains are the same =
except for some identifiers to distinguish the two blockchains.</div><div>T=
he coins on one blockchains cannot be sent to the other one or interfered b=
y the other blockchain (=C2=A0 considering so many hard forks in the last y=
ear, the replay protection should work in this situation)</div><div>Everyon=
e get double bitcoins. Each has half=C2=A0 value of original one bitcoin.=
=C2=A0</div><div>Then, we have two almost same blockchains and the capacity=
 of the original blockchain is doubled theoretically.</div><div>When sendin=
g coin, the wallet should select one blockchain randomly and try to send th=
rough only=C2=A0 one blockchain (If there is enough bitcoins)</div><div>I t=
hink it is a=C2=A0 possible solution, if the community realize=C2=A0 no pre=
viously owned asset value=C2=A0 is lost.</div><div><br></div><div>The metho=
d is inspired by the <a href=3D"https://en.wikipedia.org/wiki/Stock_split">=
stock split</a>.</div><div>When a stock share is split, for example into tw=
o shares, the price halves.</div><div>The market capitalization remains the=
 same.</div><div>There is no dilution of every shareholders&#39; total asse=
ts.</div><div><br></div><div>The bitcoin often emphasizes that the total co=
in supply should not be changed.</div><div>If the total supply increases, t=
he value of a single coin will be diluted.</div><div>That is true.</div><di=
v>However, the bad part of inflation of fiat money is not=C2=A0 diluted val=
ue of every unit of fiat money caused by total supply increase.</div><div>T=
he problem is the increased supply is not delivered to everyone proportiona=
l to their previously owned money.</div><div>The increased supply is releas=
ed through debt expansion.</div><div>The people that can borrow more money =
with low interest ratio (during QE, it was nearly 0) can invest=C2=A0 and g=
et profit.</div><div>Or they don&#39;t even need to pay back the debt. The =
debt is left to government, which might never pay back the debt, and some=
=C2=A0 get more money from government.</div><div>Others&#39; money are dilu=
ted.</div><div><br></div><div>With voluntary split of bitcoin, dilution of =
anyone&#39;s bitcoin assets won&#39;t happen.</div><div><br></div><div><br>=
</div><div><br></div><div><br></div><div><br></div></div>

--94eb2c06a2ee4d6e5d0562f42dac--