Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SXitc-0004k9-3R for bitcoin-development@lists.sourceforge.net; Fri, 25 May 2012 01:00:48 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.175 as permitted sender) client-ip=209.85.216.175; envelope-from=gmaxwell@gmail.com; helo=mail-qc0-f175.google.com; Received: from mail-qc0-f175.google.com ([209.85.216.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1SXitb-0001zJ-Az for bitcoin-development@lists.sourceforge.net; Fri, 25 May 2012 01:00:47 +0000 Received: by qcso7 with SMTP id o7so376663qcs.34 for ; Thu, 24 May 2012 18:00:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.135.199 with SMTP id o7mr580804qct.28.1337907641890; Thu, 24 May 2012 18:00:41 -0700 (PDT) Received: by 10.229.55.83 with HTTP; Thu, 24 May 2012 18:00:41 -0700 (PDT) In-Reply-To: References: <201205250045.24540.luke@dashjr.org> Date: Thu, 24 May 2012 21:00:41 -0400 Message-ID: From: Gregory Maxwell To: Jeff Garzik Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 (gmaxwell[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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SXitb-0001zJ-Az Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Punishing empty blocks? 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: Fri, 25 May 2012 01:00:48 -0000 On Thu, May 24, 2012 at 8:51 PM, Jeff Garzik wrote: > which ones are the lazy miners (> 120 seconds since last block). It's important to understand the motivations before acting=E2=80=94 otherwi= se you'll fail to do anything useful. E.g. if they're empty because some miners want to drive up fees or fight against the rapidly increasing blockchain size there isn't much you can do there. If they're empty because they're mined by botnets which don't have a local copy of the chain in order to load their victims less (and avoid central pooling) then you want something like https://bitcointalk.org/index.php?topic=3D68396.0 If they're produced by people who think they gain a mining speed advantage by not including them then then we need education=E2=80=94 droppi= ng their blocks won't help much: we've seen miners go a month with 100% of their blocks being orphaned.