From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XY5ZL-00062Z-8M for bitcoin-development@lists.sourceforge.net; Sun, 28 Sep 2014 03:54:43 +0000 X-ACL-Warn: Received: from mail-pd0-f173.google.com ([209.85.192.173]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XY5ZK-0004B6-3n for bitcoin-development@lists.sourceforge.net; Sun, 28 Sep 2014 03:54:43 +0000 Received: by mail-pd0-f173.google.com with SMTP id w10so5589343pde.4 for ; Sat, 27 Sep 2014 20:54:36 -0700 (PDT) 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 :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gb5sG293PxeVm3DcW9jBA1uxLO85JpW3o0bqkLfPi0Q=; b=apEk2b546din7AEjCL4DSE2zd/mIXVoJi4ReIYn39uMFVNVWx7WJ5t6ax9+BvwThF0 3aw1DHkcbf57ffzZzuAZF681LXFvRU6yKXOVkz/gEgomyF2gH42bszOdJCRgLnuTnWt7 DqdsFsrEYzLdjuxz+Dtld1+PxCETRWGbD9z4rNBIkAJuXbUIL9+gBdtIORMdIPelcj0g VZ0OTXLjl2Ds3SFS5YT1w7jRPDgzL6MmmwiGJZNmNG1aupKIpHOWPyLfCKIkPEG559q7 xfQ1ny2Iu+BTleXIaLJoJTWSkpjgTB0MR8zSZwTx0wP8AZUzhvNP7WBNOyPJaAbop15I WZJw== X-Gm-Message-State: ALoCoQlAn+ZGEM6RwHkeK8qr0iBnMBbL/jmrNoyp70yo0JmL50NokBxOg4PCT1wOfRpkuyHPSsIp X-Received: by 10.70.136.65 with SMTP id py1mr32772796pdb.116.1411872941784; Sat, 27 Sep 2014 19:55:41 -0700 (PDT) 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 qe9sm8619539pdb.96.2014.09.27.19.55.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Sep 2014 19:55:41 -0700 (PDT) Message-ID: <542778B0.7090202@thinlink.com> Date: Sat, 27 Sep 2014 19:55:44 -0700 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: Aaron Voisine References: <1447373.AzvO89eGJS@crushinator> <6165581.aoAyGZkGge@crushinator> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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: 1XY5ZK-0004B6-3n Cc: Bitcoin Development Subject: Re: [Bitcoin-development] SPV clients and relaying double spends 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: Sun, 28 Sep 2014 03:54:43 -0000 On 9/25/2014 7:37 PM, Aaron Voisine wrote: > Of course you wouldn't want nodes to propagate alerts without > independently verifying them How would a node independently verify a double-spend alert, other than by having access to an actual signed double-spend? #4570 relays the first double-spend AS an alert. Running this branch on mainnet, I have been keeping a live list of relayed double-spend transactions at http://respends.thinlink.com