Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XiqjW-0005Pk-IK for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 20:17:44 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bluematt.me designates 192.241.179.72 as permitted sender) client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from mail.bluematt.me ([192.241.179.72]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XiqjV-0002q5-Iv for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 20:17:42 +0000 Received: from [172.17.0.2] (gw.vpn.bluematt.me [162.243.132.6]) by mail.bluematt.me (Postfix) with ESMTPSA id DC9D350047 for ; Mon, 27 Oct 2014 20:17:35 +0000 (UTC) Message-ID: <544EA85E.8010400@bluematt.me> Date: Mon, 27 Oct 2014 20:17:34 +0000 From: Matt Corallo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <544EA3D7.2050901@thinlink.com> In-Reply-To: <544EA3D7.2050901@thinlink.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.1 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1XiqjV-0002q5-Iv 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: Mon, 27 Oct 2014 20:17:44 -0000 It is a very bad idea to delay relaying/accepting blocks based on information which is only local to your node (ie would create the ability for people to split the network by sending out lots of double-spends to different parts of the network at the same time). Thus, miners are incentivized to go connect to everyone on the network and look for double-spends, not including them in their blocks to avoid being delayed (which is OK, except having to connect to everyone is bad). There is a related concept of "discouraging" blocks which generally only refers to mining on a previous block, but you have to be careful doing that so you dont break consensus. On 10/27/14 19:58, Tom Harding wrote: > Greetings Bitcoin Dev, > > This is a proposal to improve the ability of bitcoin users to rely on > unconfirmed transactions. It can be adopted incrementally, with no hard > or soft fork required. > > https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md > > Your thoughtful feedback would be very much appreciated. > > It is not yet implemented anywhere. > > Cheers, > Tom Harding > CA, USA > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >