Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YPNAs-0000Ki-91 for bitcoin-development@lists.sourceforge.net; Sun, 22 Feb 2015 03:25:42 +0000 Received: from mail-we0-f177.google.com ([74.125.82.177]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YPNAo-0000yv-Rt for bitcoin-development@lists.sourceforge.net; Sun, 22 Feb 2015 03:25:42 +0000 Received: by wesx3 with SMTP id x3so12119830wes.7 for ; Sat, 21 Feb 2015 19:25:32 -0800 (PST) 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=nfRqgRfIuwaE/qQyj6le+BPBZt3YuBcgY+lXVHRgP30=; b=RhcegK/ufMdlPbzaA9IUwl7+sEoiIpbEtQuS646dm4Eh4MAO69irjkcurXTqpFBMp8 RTm3KCfNDYtInkmsaBXAJNin4EyBaaewZf6Bgd22JY3QSKvCD9SqetDVc8vGrCAhm+w2 0ztIENreS8O0h122Od2OMF5LYmY5Zmk1N2Ye4OWv03mtmZdfxhooqFKr/35oo78gEUSE fLOnzZGht5v6hyR7mO7Cq7yFRqIVSQH9U02gpRB3pngtEcOXlUIgp3kUxuz9KF7nqW15 kNurCdDgNtrQsmP10Bgjvq02lS6I8mP/MFq4ImZaLb8FhrP54upY+1uBILVIggixpDUY GwHQ== X-Gm-Message-State: ALoCoQng7HNHqr4tql0FfKLww7gLeY1rBe43nzmXINKB3L3mLrYqho0Xki9v6fnjlXIzZR7UH5Kj MIME-Version: 1.0 X-Received: by 10.194.133.68 with SMTP id pa4mr9795293wjb.26.1424575532489; Sat, 21 Feb 2015 19:25:32 -0800 (PST) Received: by 10.194.133.74 with HTTP; Sat, 21 Feb 2015 19:25:32 -0800 (PST) X-Originating-IP: [173.228.107.141] In-Reply-To: References: <20150212064719.GA6563@savin.petertodd.org> <20150215212512.GR14804@nl.grid.coop> <54E11248.6090401@gmail.com> <20150219085604.GT14804@nl.grid.coop> Date: Sun, 22 Feb 2015 04:25:32 +0100 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Jeff Garzik Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.9 FUZZY_AMBIEN BODY: Attempt to obfuscate words in spam -0.9 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YPNAo-0000yv-Rt Cc: Bitcoin Development Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 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: Sun, 22 Feb 2015 03:25:42 -0000 On Sat, Feb 21, 2015 at 11:47 PM, Jeff Garzik wrote: > "scorched earth" refers to the _real world_ impact such policies would > have on present-day 0-conf usage within the bitcoin community. When I posted this: http://sourceforge.net/p/bitcoin/mailman/message/32263765/ Peter Todd clarified that the concept was referred to as "scorched earth" http://sourceforge.net/p/bitcoin/mailman/message/32264039/ Like I said I don't like the name and would prefer "stag hunting" which is more formal and precise. Some people seem to use the same term for "the potential undesirable consequences of widely deployed replace-by-fee policies". I'm not sure that concept deserves its own term. > All payment processors AFAIK process transactions through some scoring > system, then accept 0-conf transactions for payments. > > This isn't some theoretical exercise. Like it or not many use > insecure 0-conf transactions for rapid payments. Deploying something > that makes 0-conf transactions unusable would have a wide, negative > impact on present day bitcoin payments, thus "scorched earth" And maybe by maintaining first seen policies we're harming the system in the long term by encouraging people to widely deploy systems based on extremely weak assumptions.