Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFLu3-0001eB-Bh; Tue, 12 Mar 2013 09:53:51 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.53 as permitted sender) client-ip=209.85.128.53; envelope-from=jtimonmv@gmail.com; helo=mail-qe0-f53.google.com; Received: from mail-qe0-f53.google.com ([209.85.128.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UFLu2-00041D-31; Tue, 12 Mar 2013 09:53:51 +0000 Received: by mail-qe0-f53.google.com with SMTP id cz11so2850939qeb.12 for ; Tue, 12 Mar 2013 02:53:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.49.84.6 with SMTP id u6mr576571qey.35.1363082024542; Tue, 12 Mar 2013 02:53:44 -0700 (PDT) Received: by 10.49.11.140 with HTTP; Tue, 12 Mar 2013 02:53:44 -0700 (PDT) In-Reply-To: References: Date: Tue, 12 Mar 2013 10:53:44 +0100 Message-ID: From: =?ISO-8859-1?B?CUpvcmdlIFRpbfNu?= To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jtimonmv[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1UFLu2-00041D-31 Cc: Bitcoin Dev , bitcoin-security@lists.sourceforge.net Subject: Re: [Bitcoin-development] Warning: many 0.7 nodes break on large number of tx/block; fork risk 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: Tue, 12 Mar 2013 09:53:51 -0000 On 3/12/13, Mike Hearn wrote: > 1) Start aggressively trying to block or down-prioritize SatoshiDice > transactions at the network level, to buy time and try to avoid > mempool exhaustion. I don't know a good way to do this, although it > appears that virtually all their traffic is actually coming via > blockchain.infos My Wallet service. During their last outage block > sizes seemed to drop to around 50kb. Alternatively, ask SD to > temporarily suspend their service (this seems like a long shot). They have a vested interested in bitcoin's success. Can't they be asked to suspend their operations temporarily until the new hard-fork is properly prepared? I thought they have stopped them already.