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 ) 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 ; 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 ) (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" To: References: In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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?