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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wcqm5-0003U9-BO for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 06:35:17 +0000 Received: from mail-pa0-f45.google.com ([209.85.220.45]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wcqm3-0005LJ-Hy for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 06:35:17 +0000 Received: by mail-pa0-f45.google.com with SMTP id kl14so444555pab.18 for ; Tue, 22 Apr 2014 23:35:09 -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:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=X0f9IHKCSRtfxcJGZTim6RQ7zbh0HETKHwap9+9J/0Y=; b=fd2y4GB7E/QweLzmIg//kQ4UrCUt+vOXtAMJhYXCP65QUezTb6QMBtRPL/B+VAN5BH CVcM/SKPkcJjUcSPSLespsBeL6udfxkVmj+HiLLEwQSgBvF9UQvYv7SR5qfVfcwfVoN/ xTCuBZGsO8mc8nX4yBPfqi0P6apE5W2OQEHzeH7FgNQlf9HfVVl32lAnCfWLIeNa97Xc d+h7heEg8xvdCkC9sdz7natjlb1sT29Ox4u0l9eOBF+viq1iHwNfmvXDpyf+S6u7ktDn gQcOioaVqywBfrlA0h0eTpCAZ+c3VutX5kvThjEuFK0H/tsSsLAGo1VaeNkzFbwLGo9c WXZw== X-Gm-Message-State: ALoCoQnaAe5TszOvASYJmSSEBD+3Af66DPAgkoEibsQVYM/kh3FO870NOoL/BEe4cQDy0ULc5S7k X-Received: by 10.68.181.165 with SMTP id dx5mr51702931pbc.38.1398234909352; Tue, 22 Apr 2014 23:35:09 -0700 (PDT) Received: from [192.168.127.212] (50-0-36-93.dsl.dynamic.sonic.net. [50.0.36.93]) by mx.google.com with ESMTPSA id pe3sm78162pbc.23.2014.04.22.23.35.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Apr 2014 23:35:08 -0700 (PDT) Message-ID: <53575F1A.2000504@monetize.io> Date: Tue, 22 Apr 2014 23:35:06 -0700 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20140422213128.GB2578@savin> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: 1Wcqm3-0005LJ-Hy Subject: Re: [Bitcoin-development] Double-spending unconfirmed transactions is a lot easier than most people realise 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: Wed, 23 Apr 2014 06:35:17 -0000 On 04/22/2014 09:29 PM, Jan Møller wrote: >>Of course, this is an especially difficult case, as you must send the >>double-spend after the original transaction - normally just sending a >>non-standard tx to Eligius first would suffice. Note how this defeats >>Andresen's double-spend-relay patch(3) as proposed since the >>double-spend is a non-standard transaction. > > Why can't you send a non-standard tx to Eligius first in this scenario?​ > Is it because LuckyBit is connected directly to Eligius, and does > Eligius relay (not only mine) non-standard transactions? > Because you only want to double-spend if you loss the bet. If you tried to double-spend every bet, there'd be no point :)