Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WdK9I-0006CK-Gf for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 13:57:12 +0000 Received: from mail-la0-f53.google.com ([209.85.215.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WdK9H-0000aT-6Z for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 13:57:12 +0000 Received: by mail-la0-f53.google.com with SMTP id ec20so2013225lab.40 for ; Thu, 24 Apr 2014 06:57:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GKlQMId/d6nq8b/9SOxaDTPZy4zlPG3e0gw6ntBEir8=; b=f7Gtrlysg2M4FQnv5csmUx2wNq0xT/01pxSlYAcrxD5firUeTTEIH5P5/jbMzcCVU6 giIxUppmcK0oIcM+ztxA2lZpTgUY6BVCRtXIKY9Fda+9beTAPoLdIQwCF8JMq0eTNCTQ nXsdQ7NxLWrkqpSrNvu9CdjeX9pKM7Gs1bLS5wvk55BAXiAdqu9nckicMKzQ2rbKv2KS 2TAcBZk5lsBU9cDJdAvlPq27MkQiuAR9JTIQHeLtzT7FTDlWgm8oyI4tuyNeiQKyAKn7 MRlgv+0q+83KOl7uT/ApE8aoiwzTVZMYSjwpjdIANngRylM7LWBO4yOT8OQCnzBbW8Rt QSrA== X-Gm-Message-State: ALoCoQk0fdhPLVWlZy80RFg+FgnI4obKBEuhSOr8XwwQTpGfJ9LEGBj7ffYzW4alFBRqIqsN1g4t MIME-Version: 1.0 X-Received: by 10.152.22.72 with SMTP id b8mr203377laf.63.1398347824547; Thu, 24 Apr 2014 06:57:04 -0700 (PDT) Received: by 10.112.185.4 with HTTP; Thu, 24 Apr 2014 06:57:04 -0700 (PDT) X-Originating-IP: [85.59.56.59] In-Reply-To: References: Date: Thu, 24 Apr 2014 15:57:04 +0200 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1WdK9H-0000aT-6Z Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks 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: Thu, 24 Apr 2014 13:57:12 -0000 On 4/24/14, Mike Hearn wrote: > No! This is a misunderstanding. The mechanism they use to prevent double > spends is to *ignore double spends*. The blocks they created indicate the > ordering of transactions they saw and proof of work is used to arrive at a > shared consensus ordering given the possibility that transactions arrived > at different times. > > I'm continually amazed at how many people seem to see the current algorithm > as the goal in and of itself, instead of an imperfect but workable means of > achieving the actual goal. I'm not saying proof of work is the goal, the goal is still p2p transaction serialization. And that's achieved through proof of work, not through "miner's honesty". > This definition of honesty is not my own, the one Bitcoin has always used. Whatever, let's keep calling stupid miners "honest miners", smart miners "dishonest-by-replace-by fee miners" and miners that do replace by fee and also hash on top of old blocks "utterly dishonest miners". > Obviously if Satoshi had wanted transactions to be double spendable by fee > in the mempool he would have made Bitcoin work that way, instead of coming > up with the nSequence based replacement scheme instead. Maybe Satoshi hadn't thought in depth about replace-by-fee when he wrote the code. Why should we care? If nSequence was a design mistake Satoshi did, should we maintain it to somehow honor him? Maybe the payment protocol shouldn't have been developed because he had some weird ideas about paying to ips? Maybe we shouldn't write any tests because he didn't do so? This persistent argument from authority is annoying. > First-seen *is* a protocol rule, as much as Set-Cookie storing data in a > browser is an HTTP protocol rule. The fact that auditing compliance with it > is harder to do than some others does not make it less of a rule. It is not a protocol rule that validators can use to discriminate the longest valid chain and therefore is not enforceable. Not even through a softfork because miners can't know which transactions other miners saw first. So if it is a protocol rule, I think it shouldn't be. > Again you are hopelessly confused. Miners that are trying to double spend > are *by definition* not making transactions irreversible, they are trying > to make transactions reversible. Miners that mine on top of the longest valid chain are helping in making transactions irreversible whether they implement a first-saw or a replace-by-fee policy. > Look at it this way. There is no inherent reason BitUndo has to undo only > Finney attacks. If it gets sufficient hash power it could offer undoing of > 1-confirm transactions too, right? Sure it'll mostly fail but that's > already a part of its business model. Sometimes it'll get two blocks in a > row and succeed. It's a very minor tweak to what they're doing. Would you > argue these miners are still useful? After all, it's impossible to be > certain after the fact that miners built on top of the "wrong" block > because forks occur naturally. That's not what I'm saying. Miners that don't mine on top of the longest chain are dishonest by my own definition as well. You want to equate replace-by-fee "dishonesty" with trying-to-rewrite-history dishonesty by saying that the transactions that "have been seen" in the network are already history and that's where we disagree. I think only what's in the chain is history and I also think that's the whole point of proof of work. And I also disagree that all the people who think this way are "hopelessly confused". We may be confused, but I think there's always hope for removing confusions provided that there's will to learn, which I think it is at least my case. > What I said is, if you believe all miners are willing to double spend for a > fee then this resolves the experiment as a failure. This is also obvious - > if you can pay miners to go back and rewrite the chain at will, Bitcoin > doesn't work. This is in fact quite polemic and thus obviously not obvious. Bitcoin works because rewriting the chain gets exponentially more expensive as time passes. > Because all miners follow this ridiculous policy, they should be willing to > fork the chain at any point to claim the higher fee on the new tx. After > ... > > Do you see now why your definition of honesty is completely broken? I see now that I may have not properly expressed myself in the earlier post since you clearly misunderstood what I meant by "smart miners". By that I mean miners implementing replace-by-fee and child-pays-for-parent policies Not miners trying to rewrite history, which I agree is about as smart as mining on top of orphan blocks.