<oembed><type>rich</type><version>1.0</version><author_name>npub15wz8j5cse6sexlw6f5q7arc5efe5hxn6kcxxyy222et8qms4u3lsemaru8</author_name><author_url>https://nostr.ae/npub15wz8j5cse6sexlw6f5q7arc5efe5hxn6kcxxyy222et8qms4u3lsemaru8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-12-29&#xA;📝 Original message:There have been no decent objections to altering the block-selection&#xA;mechanism (when two block solutions appear at nearly the same time) as&#xA;described at&#xA;&#xA;http://bitcoin.stackexchange.com/questions/39226&#xA;&#xA;Key components are:&#xA;&#xA;   - Compute BitcoinDaysDestroyed using only transactions that have been in&#xA;   your mempool for some time as oBTCDD (&#34;old BTCDD&#34;).&#xA;   - Use &#34;nearly the same time&#34; to mean separated in time by your guess of&#xA;   the average duration of block propagation times.&#xA;   - When two block solutions come in at nearly the same time, build on the&#xA;   one that has the most oBTCDD, rather than the one that came in first.&#xA;&#xA;The goal of this change is to reduce the profitability of withholding block&#xA;solutions by severely reducing the chances that a block solved a while ago&#xA;can orphan one solved recently.  &#34;Came in first&#34; seems more easily gamed&#xA;than &#34;most oBTCDD&#34;.  As I wrote there, &#34;*old coins* is always a dwindling&#xA;resource and *global nodes willing to help cheat* is probably a growing&#xA;one.&#34;&#xA;&#xA;I will write a BIP if anyone agrees it&#39;s a good idea.&#xA;&#xA;On Mon, Dec 28, 2015 at 12:26 PM, Ivan Brightly via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; On Mon, Dec 28, 2015 at 2:12 PM, Peter Todd via bitcoin-dev &lt;&#xA;&gt;&gt; bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;&gt; Far more concerning is network propagation effects between large and&#xA;&gt;&gt; small miners. For that class of issues, if you are in an environemnt&#xA;&gt;&gt; where selfish mining is possible - a fairly flat, easily DoS/sybil&#xA;&gt;&gt; attacked network topology - the profitability difference between small&#xA;&gt;&gt; and large miners even *without* attacks going on is a hugely worrying&#xA;&gt;&gt; problem. OTOH, if you&#39;re blocksize is small enough that propagation time&#xA;&gt;&gt; is negligable to profitability, then selfish mining attacks with &lt;30%&#xA;&gt;&gt; hashing power aren&#39;t much of a concern - they&#39;ll be naturally defeated&#xA;&gt;&gt; by anti-DoS/anti-sybil measures.&#xA;&gt;&gt;&#xA;&gt;&#xA;&gt; Let&#39;s agree that one factor in mining profitability is bandwidth/network&#xA;&gt; reliability/stability. Why focus on that vs electricity contracts or&#xA;&gt; vertically integrated chip manufacturers? Surely, sufficient network&#xA;&gt; bandwidth is a more broadly available commodity than &lt;$0.02/kwh&#xA;&gt; electricity, for example. I&#39;m not sure that your stranded hydroelectric&#xA;&gt; miner is any more desirable than thousands of dorm room miners with access&#xA;&gt; to 10gbit university connections and free electricity.&#xA;&gt;&#xA;&gt; _______________________________________________&#xA;&gt; bitcoin-dev mailing list&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&gt;&#xA;&gt;&#xA;&#xA;&#xA;-- &#xA;I like to provide some work at no charge to prove my value. Do you need a&#xA;techie?&#xA;I own Litmocracy &lt;http://www.litmocracy.com&gt; and Meme Racing&#xA;&lt;http://www.memeracing.net&gt; (in alpha).&#xA;I&#39;m the webmaster for The Voluntaryist &lt;http://www.voluntaryist.com&gt; which&#xA;now accepts Bitcoin.&#xA;I also code for The Dollar Vigilante &lt;http://dollarvigilante.com/&gt;.&#xA;&#34;He ought to find it more profitable to play by the rules&#34; - Satoshi&#xA;Nakamoto&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151229/654898a2/attachment.html&gt;</html></oembed>