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
|
Return-Path: <admin@glados.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1A05810C6
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 14 Sep 2015 15:13:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f176.google.com (mail-yk0-f176.google.com
[209.85.160.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 88AB01E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 14 Sep 2015 15:13:10 +0000 (UTC)
Received: by ykdt18 with SMTP id t18so135411814ykd.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 14 Sep 2015 08:13:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=lsMbyBrhOlKH/HPi3ylC9o4VDsbqFG4xjtM4I3nY58o=;
b=AfFNmfedm/je1xa3RC5zfK+ggFF+TRd8EE3CkHTHaeWrovnKBNT4OuTOctqaPU6F8r
1ck9VJyVmQrjhVEaa5MoaZ+AUw9Cffl8U1rRUN94aIsMq/m2w7TccgFE2/ET+BBmXgrB
LhDT2rqtYe+1FtH9PacGjrGiHXZVQLIIVIMDBAjK0MVKYrditlhu2WMlsF70+iF3wnnr
/RgUTQeFhTnB0MdZgeBzXBsHczH2coubadPAi1l/tjaDQxb/gF0+CYq0hP9yq+zDbjqi
bwdf8N2uIblNzH1mTG+t1Y1bvabYgZ+XLIbnvG3sSQt4IgKrJcNTNYUtFpJT+TE5h6Gx
D+ZA==
X-Gm-Message-State: ALoCoQl+P/UOvsxl4Shfnw+KZX3rVkKTca2FrvJyGI9c8EvH0oo1vA1akKoEdziUjSnj6wj75FYX
MIME-Version: 1.0
X-Received: by 10.129.108.84 with SMTP id h81mr14008556ywc.134.1442243589798;
Mon, 14 Sep 2015 08:13:09 -0700 (PDT)
Received: by 10.37.61.69 with HTTP; Mon, 14 Sep 2015 08:13:08 -0700 (PDT)
X-Originating-IP: [49.181.20.28]
Received: by 10.37.61.69 with HTTP; Mon, 14 Sep 2015 08:13:08 -0700 (PDT)
In-Reply-To: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>
References: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>
Date: Tue, 15 Sep 2015 01:13:08 +1000
Message-ID: <CAL7-sS2HG2zbFqfzboe3LHhthwtBzZSR3pMtPikx-8fL8XD4sA@mail.gmail.com>
From: gladoscc <admin@glados.cc>
To: Jason Livesay <ithkuil@gmail.com>
Content-Type: multipart/alternative; boundary=001a114dc34cd9af08051fb6806b
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Quick Bitcoin/Pre-Christmas modest blocksize max
increase
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 14 Sep 2015 15:13:11 -0000
--001a114dc34cd9af08051fb6806b
Content-Type: text/plain; charset=UTF-8
I appreciate your interest in Bitcoin, but I trust that you understand your
proposal adds nothing to the current discussion and recommend you read more
emails from this mailing list.
On 14/09/2015 11:47 am, "Jason Livesay via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> After studying the issues I believe that the situation warrants a
> short-term modest blockchain increase. Somewhere between 2mb-5mb, whatever
> the community will swallow. I recommend that happen before the winter
> shopping rush.
>
> Then, because of the fundamental technical limitations of scaling, a new
> system needs to be adopted for fast transactions. To maintain momentum
> etc., the new system ultimately settles with traditional bitcoins.
>
> In order to keep the existing brand momentum, network, and business
> investment, I believe the smoothest path forward is to build a new,
> additional system re-using the bitcoin name. I suggest this new system
> come packaged with the bitcoin core client and be referred to as
> QuickBitcoin or qbtc or something similar. As far as the public is
> concerned it could simply continue to be called bitcoin. The system will
> work on top of traditional bitcoins but have a mechanism for more/faster
> transactions. Exactly what mechanism doesn't have to be perfect, it just
> needs to be reasonably secure/useful and something that the community will
> accept.
>
> I believe this is the best way to scale bitcoin while maintaining the
> strength of its existing network, community, and branding.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--001a114dc34cd9af08051fb6806b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">I appreciate your interest in Bitcoin, but I trust that you =
understand your proposal adds nothing to the current discussion and recomme=
nd you read more emails from this mailing list. </p>
<div class=3D"gmail_quote">On 14/09/2015 11:47 am, "Jason Livesay via =
bitcoin-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.o=
rg">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br type=3D"attribu=
tion"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">After studying the issu=
es I believe that the situation warrants a short-term modest blockchain inc=
rease.=C2=A0 Somewhere between 2mb-5mb, whatever the community will swallow=
.=C2=A0 I recommend that happen before the winter shopping rush.</p>
<p dir=3D"ltr">Then, because of the fundamental technical limitations of sc=
aling, a new system needs to be adopted for fast transactions.=C2=A0 To mai=
ntain momentum etc., the new system ultimately settles with traditional bit=
coins.</p>
<p dir=3D"ltr">In order to keep the existing brand momentum, network, and b=
usiness investment, I believe the smoothest path forward is to build a new,=
additional system re-using the bitcoin name.=C2=A0 I suggest this new syst=
em come packaged with the bitcoin core client and be referred to as QuickBi=
tcoin or qbtc or something similar.=C2=A0 As far as the public is concerned=
it could simply continue to be called bitcoin.=C2=A0 The system will work =
on top of traditional bitcoins but have a mechanism for more/faster transac=
tions.=C2=A0 Exactly what mechanism doesn't have to be perfect, it just=
needs to be reasonably secure/useful and something that the community will=
accept.</p>
<p dir=3D"ltr">I believe this is the best way to scale bitcoin while mainta=
ining the strength of its existing network,=C2=A0 community, and branding.<=
br></p>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div>
--001a114dc34cd9af08051fb6806b--
|
