summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Garzik <jgarzik@exmulti.com>2012-06-15 13:17:18 -0400
committerbitcoindev <bitcoindev@gnusha.org>2012-06-15 17:17:26 +0000
commitbe01bfa7a320a4e10c4b7ec62c8d8c5ff74fe505 (patch)
tree1cc283cac5be48356803a3e6fd00473e42603850
parent16accfdac9b7211feebbb60cec9aadd95de24699 (diff)
downloadpi-bitcoindev-be01bfa7a320a4e10c4b7ec62c8d8c5ff74fe505.tar.gz
pi-bitcoindev-be01bfa7a320a4e10c4b7ec62c8d8c5ff74fe505.zip
[Bitcoin-development] SatoshiDice and Near-term scalability
-rw-r--r--50/38641b30c5792806f8b0bf1f58ad9d78a92f6e84
1 files changed, 84 insertions, 0 deletions
diff --git a/50/38641b30c5792806f8b0bf1f58ad9d78a92f6e b/50/38641b30c5792806f8b0bf1f58ad9d78a92f6e
new file mode 100644
index 000000000..dd782a212
--- /dev/null
+++ b/50/38641b30c5792806f8b0bf1f58ad9d78a92f6e
@@ -0,0 +1,84 @@
+Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <jgarzik@exmulti.com>) id 1Sfa9G-0001YU-8J
+ for bitcoin-development@lists.sourceforge.net;
+ Fri, 15 Jun 2012 17:17:26 +0000
+X-ACL-Warn:
+Received: from mail-lb0-f175.google.com ([209.85.217.175])
+ by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1Sfa9F-0007PB-Db
+ for bitcoin-development@lists.sourceforge.net;
+ Fri, 15 Jun 2012 17:17:26 +0000
+Received: by lbol5 with SMTP id l5so3412671lbo.34
+ for <bitcoin-development@lists.sourceforge.net>;
+ Fri, 15 Jun 2012 10:17:18 -0700 (PDT)
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=google.com; s=20120113;
+ h=mime-version:x-originating-ip:date:message-id:subject:from:to:cc
+ :content-type:x-gm-message-state;
+ bh=f3320VeV0FfA5wJDu+TmkDtSUn7ElRxBtyZ4Hgvu2qw=;
+ b=m2lutm+2kvnQ0d++2ZZw9VIBFM774c6zF4g2o5TQedR5zqxD91hHAu1n3wfUFw04A+
+ g9uLnToVu+LSzy3r4SAcwI6dkQIRkPZn2PVHlgpOTbyfTbIwpYg7IY1kJ/hpkOPNsZZq
+ s1S6XJgfY1oz3QoRPoHTaUhbxQatNba3MjAOMKsBqjy0IYmUZ4CFas7GneSl4DDioGK+
+ TX2g5EUlkdhfCEl9JU6T2qAnvOvYr/WR3uZ0DSUl+zVmmrwAae0V48xIVD+/JJI0HFih
+ Zdn9iDUlrAaI6Rk6pQxfhI3GlHZemmdznV309XlzcMMsLvrEqI535kX6Q6lni8uwHzbi
+ HDxw==
+MIME-Version: 1.0
+Received: by 10.112.25.100 with SMTP id b4mr2850792lbg.55.1339780638616; Fri,
+ 15 Jun 2012 10:17:18 -0700 (PDT)
+Received: by 10.114.19.70 with HTTP; Fri, 15 Jun 2012 10:17:18 -0700 (PDT)
+X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
+Date: Fri, 15 Jun 2012 13:17:18 -0400
+Message-ID: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com>
+From: Jeff Garzik <jgarzik@exmulti.com>
+To: bitcoin-development@lists.sourceforge.net
+Content-Type: text/plain; charset=ISO-8859-1
+X-Gm-Message-State: ALoCoQnCTEisBAX3qa8lCspCboLk4TqxoQbV6jBgSd2JvsgPUwf3nh7PWcjxYCZLMuPkCJbBvKTt
+X-Spam-Score: 0.0 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+X-Headers-End: 1Sfa9F-0007PB-Db
+Subject: [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: Fri, 15 Jun 2012 17:17:26 -0000
+
+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
+
+