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 <jgarzik@exmulti.com>) id 1SXayZ-0001Da-Lt for bitcoin-development@lists.sourceforge.net; Thu, 24 May 2012 16:33:23 +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 1SXayV-0002Zi-K0 for bitcoin-development@lists.sourceforge.net; Thu, 24 May 2012 16:33:23 +0000 Received: by lbol5 with SMTP id l5so8625488lbo.34 for <bitcoin-development@lists.sourceforge.net>; Thu, 24 May 2012 09:33:13 -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 :content-type:x-gm-message-state; bh=yQY92Ggm02d/tcMilNjBZ0kek6ASJOEKFdrzhlIUaXk=; b=LpAr1OIe6FeGY/6NAntJL0tM/8f3IBAc/gnt/ORZ1szTDP3eYvEIQhXJzRN1fYYELi tI7tGI7/8odAc6E4ca0+blVopLNxmZGv+zRsxhOaFUyyHVeMhmGVUZ++da+7SXqbeRZU hbFtFzo850nRC9VF+CVM4PnlI0MTipvGA+ihcsull92JuWhl5R3bsjQN+UwrKSCnhpxH BoF4Ws7jmRodJWsUonsX8Qc/r3VMqYPBglCgc1YASgpDbsOtSFk/AoDEjJmQMBlUy38b WmVZDjZfO3mX2yEghyyqi6Z3dnkADHrQLq91RcBK6kEXWSJw0nRBbzVOqTZGKIuPvZxV 4Kvg== MIME-Version: 1.0 Received: by 10.112.46.101 with SMTP id u5mr50839lbm.21.1337877192953; Thu, 24 May 2012 09:33:12 -0700 (PDT) Received: by 10.114.0.103 with HTTP; Thu, 24 May 2012 09:33:12 -0700 (PDT) X-Originating-IP: [99.43.178.25] Date: Thu, 24 May 2012 12:33:12 -0400 Message-ID: <CA+8xBpdBe4yR6xkCODL6JQ41Gyx9eWcGGGvcQVt7DCmaEnAhbg@mail.gmail.com> From: Jeff Garzik <jgarzik@exmulti.com> To: Bitcoin Development <bitcoin-development@lists.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmLEvymyQygIwafuqy+Scu6lRtQEXC5VgC3HlwQPohlHHqQTiNtiwMTYvypoQBUXr0bnwQT X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SXayV-0002Zi-K0 Subject: [Bitcoin-development] Punishing empty blocks? 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: Thu, 24 May 2012 16:33:23 -0000 There appears to be some non-trivial mining power devoted to mining empty blocks. Even with satoshi's key observation -- hash a fixed 80-byte header, not the entire block -- some miners still find it easier to mine empty blocks, rather than watch the network for new transactions. Therefore I was wondering what people thought about a client implementation change: - Do not store or relay empty blocks, if time since last block < X (where X = 60 minutes, perhaps) or even stronger, - Ensure latest block includes at least X percent of mempool unconfirmed TXs The former is easier to implement, though there is the danger that no-TX miners simply include a statically generated transaction or two. The latter might be considered problematic, as it might refuse to relay quickly found blocks. Comments? It wouldn't be a problem if these no-TX blocks were not already getting frequent (1 in 20). -- Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com