Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XmWpS-0005Wq-6S for bitcoin-development@lists.sourceforge.net; Thu, 06 Nov 2014 23:51:02 +0000 X-ACL-Warn: Received: from mail-pa0-f44.google.com ([209.85.220.44]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XmWpR-0005xh-3N for bitcoin-development@lists.sourceforge.net; Thu, 06 Nov 2014 23:51:02 +0000 Received: by mail-pa0-f44.google.com with SMTP id bj1so2278425pad.17 for ; Thu, 06 Nov 2014 15:50:55 -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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=V55WYnILdyWHnQ6ADE1HL1n4Hz0bIlkxHiUB7nnsQ4o=; b=CPJs2f399jig093X9Cf48nsTsAuqIsuaebX2oCnaqJM6jQCxLSR+0FkTepp5dg4Fei U2fQGwFc8Ru96bxQWnlT7+xAKDK5E0bMmHGe2NSftPmAHJv5ToOGCmXENyB9u6yPH3LE 2iHJxKs8IebWXVZb8cP46ckdHlyeZCVfvBsMT8tTl7pd8H+fB+beiyP7sCmxXtNAitRx umecLIhSwFXehxh4DOBHV+filwNyB2qNfPeyeJg1HT/tNCagKRVBUSpgUS3JxksFB3UY vbyinYosF5z85GIm3rwBXGdalEKYJ8k5OwI+sN3H0oTe2t2i2nbaHr+LvTZKZ/rv2W71 PYHg== X-Gm-Message-State: ALoCoQnYIhxtQxlWfz85mnYU/0J7FfmnqZ1+lglkKJQL/xf/n+4xlcYVC7M391KFNF3EVgNdCZYw X-Received: by 10.66.180.166 with SMTP id dp6mr7845456pac.101.1415317855384; Thu, 06 Nov 2014 15:50:55 -0800 (PST) Received: from [192.168.1.89] (99-6-44-248.lightspeed.sntcca.sbcglobal.net. [99.6.44.248]) by mx.google.com with ESMTPSA id b16sm4442410pbu.59.2014.11.06.15.50.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Nov 2014 15:50:53 -0800 (PST) Message-ID: <545C095D.4010703@thinlink.com> Date: Thu, 06 Nov 2014 15:50:53 -0800 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Bitcoin Development References: <544EA3D7.2050901@thinlink.com> <544EA85E.8010400@bluematt.me> <544EFEE8.4000000@thinlink.com> <544FD47F.6060900@thinlink.com> In-Reply-To: <544FD47F.6060900@thinlink.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: 1XmWpR-0005xh-3N Subject: Re: [Bitcoin-development] DS Deprecation Window 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, 06 Nov 2014 23:51:02 -0000 Added a section "Confidence to include tx1" and subsection "Deliberate delay attack" https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md I found that under concerted attack, if miner excludes any transaction first seen less than 30 seconds ago, or double-spent less than 30 seconds after first seen, he should expect 5 of 10000 nodes to delay his block. Hal Finney remarked that this idea would need "careful analysis." More help is very welcome. https://bitcointalk.org/index.php?topic=3441.msg48789#msg48789 Cheers! On 10/28/2014 10:38 AM, Tom Harding wrote: > So, I think it will be possible to quantify and target the risk of > including tx1... >