public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jonathan Warren" <jonathan@bitcoinstats•org>
To: <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
Date: Fri, 15 Jun 2012 22:35:13 -0400	[thread overview]
Message-ID: <007701cd4b68$a88e6a40$f9ab3ec0$@bitcoinstats.org> (raw)
In-Reply-To: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com>

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?





  parent reply	other threads:[~2012-06-16  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 17:17 Jeff Garzik
2012-06-15 17:52 ` Stefan Thomas
2012-06-16  2:35 ` Jonathan Warren [this message]
2012-06-16  4:33   ` Amir Taaki
2012-06-16  8:30     ` Mike Hearn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='007701cd4b68$a88e6a40$f9ab3ec0$@bitcoinstats.org' \
    --to=jonathan@bitcoinstats$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox