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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1YHXq3-00065H-Nu
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 13:11:51 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.44 as permitted sender)
client-ip=74.125.82.44; envelope-from=laanwj@gmail.com;
helo=mail-wg0-f44.google.com;
Received: from mail-wg0-f44.google.com ([74.125.82.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YHXq2-0004a1-Rw
for bitcoin-development@lists.sourceforge.net;
Sat, 31 Jan 2015 13:11:51 +0000
Received: by mail-wg0-f44.google.com with SMTP id z12so31345548wgg.3
for <bitcoin-development@lists.sourceforge.net>;
Sat, 31 Jan 2015 05:11:44 -0800 (PST)
X-Received: by 10.180.207.66 with SMTP id lu2mr4667154wic.13.1422709904840;
Sat, 31 Jan 2015 05:11:44 -0800 (PST)
Received: from amethyst.lan (e107003.upc-e.chello.nl. [213.93.107.3])
by mx.google.com with ESMTPSA id cm7sm11196890wib.6.2015.01.31.05.11.43
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sat, 31 Jan 2015 05:11:43 -0800 (PST)
Date: Sat, 31 Jan 2015 14:11:42 +0100 (CET)
From: Wladimir <laanwj@gmail.com>
To: Nick Simpson <imsaguy@gmail.com>
In-Reply-To: <CAOiKAtox1qmOEO6m9_ZjjR9QSqAGZv5s6YcBHq7oRnmNirdM=Q@mail.gmail.com>
Message-ID: <alpine.DEB.2.10.1501311341580.21504@nzrgulfg.ivfhpber.pbz>
References: <CADZB0_aWkSApjRA-WQcVsonOTpZNX8=G=iuY3k+dKSwDq=xM6A@mail.gmail.com>
<CAOiKAtox1qmOEO6m9_ZjjR9QSqAGZv5s6YcBHq7oRnmNirdM=Q@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-59247149-1422709903=:21504"
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
2.8 MALFORMED_FREEMAIL Bad headers on message from free email service
0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YHXq2-0004a1-Rw
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Is there a way to estimate the maximum
number of transactions per minute Bitcoin can handle as it is today?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 13:11:51 -0000
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323328-59247149-1422709903=:21504
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
On Fri, 30 Jan 2015, Nick Simpson wrote:
> This has been discussed before. I believe most people don't expect Bitcoin to replace all of the various methods of payment. Scalability is
> always a concern, just not to the level of Alipay this year (or the next or the next for that matter.)
Yes, that about summarizes it.
The block chain is a single channel broadcasted over the entire
world, and I don't believe it will ever be possible nor desirable to broadcast all the
world's transactions over one channel.
The everyone-validates-everything approach doesn't scale. It is however
useful to settle larger transactions in an irreversible, zero-trust way.
That's what makes the bitcoin system, as it is now, valuable.
But it is absurd for the whole world to have to validate every purchase of
a cup of coffee or a bus ticket by six billion others.
Naively scaling up the block size will get some leeway in the short term,
but I believe a future scalable payment system based on bitcoin will be
mostly based on off-blockchain transactions (in some form) or that there
will be a hierarchical or subdivided system (e.g. temporary or per-locale
sidechains).
Wladimir
--8323328-59247149-1422709903=:21504--
|
