Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YM2sf-0000I6-AQ for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 23:09:09 +0000 X-ACL-Warn: Received: from mail-pa0-f47.google.com ([209.85.220.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YM2se-0005IR-Ed for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 23:09:09 +0000 Received: by mail-pa0-f47.google.com with SMTP id lf10so14554633pab.6 for ; Thu, 12 Feb 2015 15:09:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mOvNG/GmBucijtJe1XmY9LplB59DsKB7NPlNHTTSGJY=; b=ARx/rXdBy8ZsAcCCTgUZx1OkznICoCavXQPEDOtgwUbr+e/HT5H1s1x1WW18X0TPtE 2clSBPJDWKJTWLROTMEvDMgcMlcsaxVtTeqkY/fn8g0R/ym0QQDcwRPl5xiyrLlEx4ZO ytI67yWU4qH2GnlALgnhlITXF2e11XtQpai8myviBXKi5lJ92qTgvcpXB8WTda5Qjxdv PFLw+IrkdOxRG8+DgC3u9fjj8HsnLU4be/74kJLSOX213sCMECeCCYVeGM3zCJyYhxhG OJXRZghtYq8BhYeDaevPPWku06i892/vUj5IH9OKH/ADuOM0sF/x4R+WZ6xJX2AGg64W fZKg== X-Gm-Message-State: ALoCoQnf/vTelyLoM/S+G0nG9BolWzS+Y7j2XrAr43P0DL56+0pIX/RbEwuyP7ps32rsV2gq4CWT X-Received: by 10.66.132.6 with SMTP id oq6mr10469077pab.29.1423782542687; Thu, 12 Feb 2015 15:09:02 -0800 (PST) Received: from [10.100.1.239] ([204.58.254.99]) by mx.google.com with ESMTPSA id ce1sm4789515pdb.34.2015.02.12.15.09.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 15:09:01 -0800 (PST) Message-ID: <54DD3271.4010205@thinlink.com> Date: Thu, 12 Feb 2015 15:08:33 -0800 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Tamas Blummer References: <20150212064719.GA6563@savin.petertodd.org> <7C80D196-AB91-44EA-B2D7-343D7214BAA8@bitsofproof.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server [204.58.254.99 listed in dnsbl.sorbs.net] X-Headers-End: 1YM2se-0005IR-Ed Cc: Bitcoin Dev 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: Thu, 12 Feb 2015 23:09:09 -0000 On 2/12/2015 6:25 AM, Tamas Blummer wrote: > > Miner will see a mixed picture and will struggle to act “honestly” on > a statistical measure. The statistics come from the aggregate actions of all nodes, especially those miners who watch p2p transactions and assemble blocks. Any one node makes deterministic decisions based on its own observation -- just like today's valid/invalid decision based on whether a blocktime is within the next 2 hours or not. The idea is that miners will exclude respends because they put the block at risk of being forked off, with no offsetting payback. The design point is to make sure this is sufficiently unlikely to happen accidentally, or via some attack vector.