summaryrefslogtreecommitdiff
path: root/46/2bbfe11ce549a69c1ee71d29f822a24b82c246
blob: dd921a42e08f81f62cea41e268e5ed76c0b620c9 (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jonathan@bitcoinstats.org>) id 1SfjC9-0008FG-Ns
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 02:57:01 +0000
X-ACL-Warn: 
Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1SfjC8-00027b-HR for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 02:57:01 +0000
Received: from hrndva-omtalb.mail.rr.com ([10.128.143.53])
	by hrndva-qmta04.mail.rr.com with ESMTP
	id <20120616023628714.PAQV10140@hrndva-qmta04.mail.rr.com>
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 16 Jun 2012 02:36:28 +0000
X-Authority-Analysis: v=2.0 cv=D8PF24tj c=1 sm=0 a=9e3N6MOxZ89Iv1uq61Cg6A==:17
	a=7Zuk48CreckA:10 a=HpGCDdIWXI4A:10 a=YHC52fuVPaIA:10
	a=raHx0Ofnui8A:10 a=kj9zAlcOel0A:10 a=POaq37HCAAAA:8
	a=juZmmhT_AAAA:8 a=FP58Ms26AAAA:8 a=tT7S5PCnve-mAYrq2QQA:9
	a=CjuIK1q_8ugA:10 a=X_HMdJ6rkoEA:10
	a=9e3N6MOxZ89Iv1uq61Cg6A==:117
X-Cloudmark-Score: 0
X-Originating-IP: 75.186.58.44
Received: from [75.186.58.44] ([75.186.58.44:4232] helo=jonwarren.org)
	by hrndva-oedge03.mail.rr.com (envelope-from
	<jonathan@bitcoinstats.org>) (ecelerity 2.2.3.46 r()) with ESMTP
	id 59/E8-13336-5E0FBDF4; Sat, 16 Jun 2012 02:35:18 +0000
Received: from atom ([66.108.252.231]) by jonwarren.org with MailEnable ESMTP;
	Fri, 15 Jun 2012 22:35:13 -0400
From: "Jonathan Warren" <jonathan@bitcoinstats.org>
To: <bitcoin-development@lists.sourceforge.net>
References: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com>
In-Reply-To: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com>
Date: Fri, 15 Jun 2012 22:35:13 -0400
Message-ID: <007701cd4b68$a88e6a40$f9ab3ec0$@bitcoinstats.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQEzqhiOZ+kqUTDFEP10b141BE5lhZgvdUGg
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [71.74.56.122 listed in list.dnswl.org]
X-Headers-End: 1SfjC8-00027b-HR
Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
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, 16 Jun 2012 02:57:01 -0000

Yes, I measure mainnet confirmation times on a regular basis.
http://bitcoinstats.org/post/tx-confirmation-times-June2012.png

Before fairly recently, fee-paying transactions never took anywhere close to
this long to be confirmed. 

Jonathan Warren
(Bitcointalk: Atheros)

-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@exmulti.com] 
Sent: Friday, June 15, 2012 1:17 PM
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] SatoshiDice and Near-term scalability

Hard-fork requires a very high level of community buy-in, because it shuts
out older clients who will simply refuse to consider >1MB blocks valid.

Anything approaching that level of change would need some good, hard data
indicating that SatoshiDice was shutting out the majority of other traffic.
Does anyone measure mainnet "normal tx" confirmation times on a regular
basis?  Any other hard data?