<oembed><type>rich</type><version>1.0</version><author_name>npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58</author_name><author_url>https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2012-05-24&#xA;📝 Original message:On Thu, May 24, 2012 at 8:45 PM, Luke-Jr &lt;luke at dashjr.org&gt; wrote:&#xA;&gt; On Thursday, May 24, 2012 4:33:12 PM Jeff Garzik wrote:&#xA;&gt;&gt; Comments?  It wouldn&#39;t be a problem if these no-TX blocks were not&#xA;&gt;&gt; already getting frequent (1 in 20).&#xA;&gt;&#xA;&gt; FWIW, based on statistics for Eligius&#39;s past 100 blocks, it seems 10% (1 in&#xA;&gt; 10) of 1-txn blocks is not actually unreasonable. This also means these 1-txn&#xA;&gt; mined blocks are not necessarily harming Bitcoin intentionally. Anyone care to&#xA;&gt; figure out the math for how fast miners need to finish processing transactions&#xA;&gt; to reduce the number of 1txn blocks?&#xA;&#xA;Look at the time since last block, and correlate with the number of&#xA;non-spam TX&#39;s in the memory pool at the time.  It is obvious which&#xA;ones are quick blocks (&lt;60 seconds since last block, no big deal) and&#xA;which ones are the lazy miners (&gt; 120 seconds since last block).&#xA;&#xA;-- &#xA;Jeff Garzik&#xA;exMULTI, Inc.&#xA;jgarzik at exmulti.com</html></oembed>