Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id ADEC4414 for ; Fri, 17 Jul 2015 12:56:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.help.org (mail.help.org [70.90.2.18]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2DEB0E9 for ; Fri, 17 Jul 2015 12:56:53 +0000 (UTC) Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA ; Fri, 17 Jul 2015 08:56:48 -0400 References: <24662b038abc45da7f3990e12a649b8a@airmail.cc> <55A66FA9.4010506@thinlink.com> <20150715151825.GB20029@savin.petertodd.org> <20150715155903.GC20029@savin.petertodd.org> <55A68668.6@bitcoins.info> <20150715193259.GC3064@muck> <20150717115920.GA19616@savin.petertodd.org> From: Milly Bitcoin To: bitcoin-dev@lists.linuxfoundation.org Message-ID: <55A8FB91.40506@bitcoins.info> Date: Fri, 17 Jul 2015 08:56:49 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150717115920.GA19616@savin.petertodd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2015 12:56:53 -0000 > My "relationships" are nothing more than people > being willing to talk to me, ask me for advice, and warn me about > possible threats. They're not legal contracts. Your actions make it appear as if you attack companies with the hope of landing consulting fees. I assume if companies hire you as a consultant or put you on some advisory board then you stop badmouthing them. These type of developer attacks are a high risk issue due to the small number of developers who have been given authority by the github gatekeeper and the lack of an incentive system for Bitcoin devlelopers. I have been suggesting a systematic risk analysis to reduce the probability of such an attack. If you have a systematic risk analysis then when there are issue you judge it against a standard. That replaces the current situation where developers haphazardly make claims in twitter, Reddit, and blog posts and create drama and confusion. Russ