<oembed><type>rich</type><version>1.0</version><author_name>npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_name><author_url>https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-24&#xA;📝 Original message:On 4/24/14, Mike Hearn &lt;mike at plan99.net&gt; wrote:&#xA;&gt; No! This is a misunderstanding. The mechanism they use to prevent double&#xA;&gt; spends is to *ignore double spends*. The blocks they created indicate the&#xA;&gt; ordering of transactions they saw and proof of work is used to arrive at a&#xA;&gt; shared consensus ordering given the possibility that transactions arrived&#xA;&gt; at different times.&#xA;&gt;&#xA;&gt; I&#39;m continually amazed at how many people seem to see the current algorithm&#xA;&gt; as the goal in and of itself, instead of an imperfect but workable means of&#xA;&gt; achieving the actual goal.&#xA;&#xA;I&#39;m not saying proof of work is the goal, the goal is still p2p&#xA;transaction serialization.&#xA;And that&#39;s achieved through proof of work, not through &#34;miner&#39;s honesty&#34;.&#xA;&#xA;&gt; This definition of honesty is not my own, the one Bitcoin has always used.&#xA;&#xA;Whatever, let&#39;s keep calling stupid miners &#34;honest miners&#34;, smart&#xA;miners &#34;dishonest-by-replace-by fee miners&#34; and miners that do replace&#xA;by fee and also hash on top of old blocks &#34;utterly dishonest miners&#34;.&#xA;&#xA;&gt; Obviously if Satoshi had wanted transactions to be double spendable by fee&#xA;&gt; in the mempool he would have made Bitcoin work that way, instead of coming&#xA;&gt; up with the nSequence based replacement scheme instead.&#xA;&#xA;Maybe Satoshi hadn&#39;t thought in depth about replace-by-fee when he&#xA;wrote the code.&#xA;Why should we care?&#xA;If nSequence was a design mistake Satoshi did, should we maintain it&#xA;to somehow honor him?&#xA;Maybe the payment protocol shouldn&#39;t have been developed because he&#xA;had some weird ideas about paying to ips? Maybe we shouldn&#39;t write any&#xA;tests because he didn&#39;t do so?&#xA;This persistent argument from authority is annoying.&#xA;&#xA;&gt; First-seen *is* a protocol rule, as much as Set-Cookie storing data in a&#xA;&gt; browser is an HTTP protocol rule. The fact that auditing compliance with it&#xA;&gt; is harder to do than some others does not make it less of a rule.&#xA;&#xA;It is not a protocol rule that validators can use to discriminate the&#xA;longest valid chain and therefore is not enforceable. Not even through&#xA;a softfork because miners can&#39;t know which transactions other miners&#xA;saw first.&#xA;So if it is a protocol rule, I think it shouldn&#39;t be.&#xA;&#xA;&gt; Again you are hopelessly confused. Miners that are trying to double spend&#xA;&gt; are *by definition* not making transactions irreversible, they are trying&#xA;&gt; to make transactions reversible.&#xA;&#xA;Miners that mine on top of the longest valid chain are helping in&#xA;making transactions irreversible whether they implement a first-saw or&#xA;a replace-by-fee policy.&#xA;&#xA;&gt; Look at it this way. There is no inherent reason BitUndo has to undo only&#xA;&gt; Finney attacks. If it gets sufficient hash power it could offer undoing of&#xA;&gt; 1-confirm transactions too, right? Sure it&#39;ll mostly fail but that&#39;s&#xA;&gt; already a part of its business model. Sometimes it&#39;ll get two blocks in a&#xA;&gt; row and succeed. It&#39;s a very minor tweak to what they&#39;re doing. Would you&#xA;&gt; argue these miners are still useful? After all, it&#39;s impossible to be&#xA;&gt; certain after the fact that miners built on top of the &#34;wrong&#34; block&#xA;&gt; because forks occur naturally.&#xA;&#xA;That&#39;s not what I&#39;m saying. Miners that don&#39;t mine on top of the&#xA;longest chain are dishonest by my own definition as well.&#xA;You want to equate replace-by-fee &#34;dishonesty&#34; with&#xA;trying-to-rewrite-history dishonesty by saying that the transactions&#xA;that &#34;have been seen&#34; in the network are already history and that&#39;s&#xA;where we disagree. I think only what&#39;s in the chain is history and I&#xA;also think that&#39;s the whole point of proof of work.&#xA;And I also disagree that all the people who think this way are&#xA;&#34;hopelessly confused&#34;. We may be confused, but I think there&#39;s always&#xA;hope for removing confusions provided that there&#39;s will to learn,&#xA;which I think it is at least my case.&#xA;&#xA;&gt; What I said is, if you believe all miners are willing to double spend for a&#xA;&gt; fee then this resolves the experiment as a failure. This is also obvious -&#xA;&gt; if you can pay miners to go back and rewrite the chain at will, Bitcoin&#xA;&gt; doesn&#39;t work.&#xA;&#xA;This is in fact quite polemic and thus obviously not obvious.&#xA;Bitcoin works because rewriting the chain gets exponentially more&#xA;expensive as time passes.&#xA;&#xA;&gt; Because all miners follow this ridiculous policy, they should be willing to&#xA;&gt; fork the chain at any point to claim the higher fee on the new tx. After&#xA;&gt; ...&#xA;&gt;&#xA;&gt; Do you see now why your definition of honesty is completely broken?&#xA;&#xA;I see now that I may have not properly expressed myself in the earlier&#xA;post since you clearly misunderstood what I meant by &#34;smart miners&#34;.&#xA;By that I mean miners implementing replace-by-fee and&#xA;child-pays-for-parent policies Not miners trying to rewrite history,&#xA;which I agree is about as smart as mining on top of orphan blocks.</html></oembed>