From: Jeff Garzik <jgarzik@exmulti•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] SatoshiDice and Near-term scalability
Date: Fri, 15 Jun 2012 13:17:18 -0400 [thread overview]
Message-ID: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com> (raw)
On Fri, Jun 15, 2012 at 12:56 PM, Stefan Thomas <moon@justmoon•de> wrote:
> The artificial limits like the block size limit are essentially putting
[...]
Changing the block size is an item for the hard-fork list. The chance
of the block size limit changing in the short term seems rather low...
it is a "nuclear option."
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?
Clearly SatoshiDice is a heavy user of the network, but there is a
vast difference between a good stress test and a network flood that is
shutting out non-SD users.
Can someone please help quantify the situation? kthanks :)
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
next reply other threads:[~2012-06-15 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 17:17 Jeff Garzik [this message]
2012-06-15 17:52 ` Stefan Thomas
2012-06-16 2:35 ` Jonathan Warren
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='CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com' \
--to=jgarzik@exmulti$(echo .)com \
--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