From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z6NKZ-0002DE-46 for bitcoin-development@lists.sourceforge.net; Sat, 20 Jun 2015 18:17:27 +0000 X-ACL-Warn: Received: from resqmta-ch2-10v.sys.comcast.net ([69.252.207.42]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.76) id 1Z6NKY-0004Zi-Br for bitcoin-development@lists.sourceforge.net; Sat, 20 Jun 2015 18:17:27 +0000 Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-10v.sys.comcast.net with comcast id iiHM1q0012S2Q5R01iHMxG; Sat, 20 Jun 2015 18:17:21 +0000 Received: from crushinator.localnet ([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0]) by resomta-ch2-16v.sys.comcast.net with comcast id iiHK1q0054eLRLv01iHLcH; Sat, 20 Jun 2015 18:17:20 +0000 From: Matt Whitlock To: Pieter Wuille Date: Sat, 20 Jun 2015 14:17:18 -0400 Message-ID: <3848127.0flgkf9F4i@crushinator> User-Agent: KMail/4.14.9 (Linux/3.18.12-gentoo; KDE/4.14.9; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [69.252.207.42 listed in list.dnswl.org] 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z6NKY-0004Zi-Br Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Hard fork via miner vote 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: Sat, 20 Jun 2015 18:17:27 -0000 On Saturday, 20 June 2015, at 8:11 pm, Pieter Wuille wrote: > you want full nodes that have not noticed the fork to fail rather than see a slow but otherwise functional chain. Isn't that what the Alert mechanism is for? If these nodes continue running despite an alert telling them they're outdated, then it must be intentional.