summaryrefslogtreecommitdiff
path: root/b2/502cce399d55051f59dfa937fd3a23fe1b948d
blob: 88af0984729f9db3bc183011b8806fe580a357f5 (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
Return-Path: <moonpunter@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 07AE8D40
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 16 Sep 2015 11:23:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com
	[209.85.218.50])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 61F9C14E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 16 Sep 2015 11:23:54 +0000 (UTC)
Received: by oixx17 with SMTP id x17so121638890oix.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 16 Sep 2015 04:23:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=reply-to:subject:to:references:from:message-id:date:user-agent
	:mime-version:in-reply-to:content-type:content-transfer-encoding;
	bh=RyWGL0SXySQQ4d9RwJAzD1j++rBzNlvVQCNrw6/Wrlw=;
	b=GMZ1fheY9E7wSA2jPpEtu0O1DHKf1hz0KIZ+zuKswLVpcPgy6RnLBPFCfGNT+OEFEL
	lCUC9pyUWcRzjb7GhBwaBIdZNXkI9QgpNIbGUzA8KAKJq5Fp1eu0txWxqGJqhxvSQG6z
	V+VMeCyKw6hvZf5Ugfo8JkvOu+O13rzeOqIff8z84xzQGDtIUtAeuC/yRQB4SQoTUKZz
	vQucKOSHX6vdItcfEvB+fBMesYroYaTAs1+yNf3BQ6pgJn2DLDO2qNT9u7Go70m2Mwmq
	r/BXF1YH9yM1yrJkNk/W43jdoeoAeM3CQOR7gM2kxGSa203DltvfVEhAFA6FKhEkSnXC
	90kg==
X-Received: by 10.182.120.100 with SMTP id lb4mr22734538obb.71.1442402633714; 
	Wed, 16 Sep 2015 04:23:53 -0700 (PDT)
Received: from [192.168.0.2] ([206.255.86.207])
	by smtp.googlemail.com with ESMTPSA id
	m133sm10919620oif.8.2015.09.16.04.23.53
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Wed, 16 Sep 2015 04:23:53 -0700 (PDT)
Reply-To: moonpunter@gmail.com
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>
From: phm <moonpunter@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <55F95148.5050504@gmail.com>
Date: Wed, 16 Sep 2015 06:23:52 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Firefox/38.0 SeaMonkey/2.35
MIME-Version: 1.0
In-Reply-To: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	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
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: Wed, 16 Sep 2015 11:23:55 -0000

Jason Livesay via bitcoin-dev wrote:
> In order to keep the existing brand momentum, network, and business
> investment,=20
These are precisely the issues that the Bitcoin Development team SHOULD
NOT concern themselves with as they are not technical in nature.
> 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.=20
A few members of the development team have already begun doing something
along these lines but its future does not look promising.

I do not see any indication that this Christmas will be any more or less
busy than last Christmas. Correct me if I'm wrong, but retail spending
as a whole still makes up only a small percentage of Bitcoin transactions=
=2E

phm
http://phm.link