Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R1kXs-00038N-H2 for bitcoin-development@lists.sourceforge.net; Thu, 08 Sep 2011 19:45:56 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1R1kXr-0005jC-QZ for bitcoin-development@lists.sourceforge.net; Thu, 08 Sep 2011 19:45:56 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 3BEDA204026 for ; Thu, 8 Sep 2011 19:45:50 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Thu, 8 Sep 2011 15:45:35 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; ) References: <1315510992.9621.140258138898885@webmail.messagingengine.com> In-Reply-To: <1315510992.9621.140258138898885@webmail.messagingengine.com> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109081545.41378.luke@dashjr.org> X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1R1kXr-0005jC-QZ Subject: Re: [Bitcoin-development] Alert System 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, 08 Sep 2011 19:45:56 -0000 On Thursday, September 08, 2011 3:43:12 PM theymos wrote: > The alert system will be very important if there are ever any critical > problems in the network. For example, it is currently Bitcoin's only > defense against an attacker with >50% of the computational power, where > alerts would be used to tell people to stop accepting transactions. I don't seem to recall this ever happening, despite Deepbit having over 50% multiple times now.