From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XGD5Z-0002Es-CY for bitcoin-development@lists.sourceforge.net; Sat, 09 Aug 2014 20:18:05 +0000 Received: from mail-qc0-f176.google.com ([209.85.216.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XGD5Y-0007Sx-13 for bitcoin-development@lists.sourceforge.net; Sat, 09 Aug 2014 20:18:05 +0000 Received: by mail-qc0-f176.google.com with SMTP id m20so448141qcx.35 for ; Sat, 09 Aug 2014 13:17:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WQaGLi2hIUyha018n0DwQ9CFRChXY0qOpnmKy34rwp8=; b=a5EpNdK6qw4rj9YJnfoqGWEu4IbO4Qf1lm6y7UkFHIp+Z7V65GJ35KexrN6bOs/YgX 1Di5mXsmUHcFgTRtEXwolEI8mGUt2hFnlchVx1H+CnQXQvq6rPoT4FWyPotVM/+RAD6P ZUud3IknDc91oxqn9qpxDJwNXiRnvdpYEjsYhw90WS8HKGtCiexTTTSuYofhlsiE6eQy CW+cYLzzQpNAe3yDCXUZoQQ0mRHyfrBUVIY1yhsRUuhXqn5I7vbMwJgjM5NFhBWrJi8r ZOTCm6SU07Sd2JIKZcev39i+mcVEg49wvvH8xHduEBKZ6uoYLTMd1izbZrTbeTulb4w3 0V3Q== X-Gm-Message-State: ALoCoQmvFwwcjyUNRawjjdfqaETAJCLxWV5X7et4EMsrLy9vcNcvsZbnx21KycRfBO1v3Yl6FMCN MIME-Version: 1.0 X-Received: by 10.140.19.100 with SMTP id 91mr34438803qgg.32.1407615478292; Sat, 09 Aug 2014 13:17:58 -0700 (PDT) Received: by 10.140.47.175 with HTTP; Sat, 9 Aug 2014 13:17:58 -0700 (PDT) X-Originating-IP: [50.0.37.37] In-Reply-To: <53E61DDA.5030307@certimix.com> References: <8137823.B0x87S28xY@calzone> <1530801.palqu9XdN4@1337h4x0r> <5456835.U3gAI91RM4@calzone> <53E61DDA.5030307@certimix.com> Date: Sat, 9 Aug 2014 13:17:58 -0700 Message-ID: From: Mark Friedenbach To: Sergio Lerner Content-Type: multipart/alternative; boundary=001a1135637e9080a90500380415 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1XGD5Y-0007Sx-13 Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] CoinShuffle: decentralized CoinJoin without trusted third parties 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, 09 Aug 2014 20:18:05 -0000 --001a1135637e9080a90500380415 Content-Type: text/plain; charset=UTF-8 On Sat, Aug 9, 2014 at 6:10 AM, Sergio Lerner wrote: > Hi Tim, > It's clear from the paper that the second party in the protocol can > de-anonymize the first party. So it's seems that dishonest shufflers would > prefer to be in that position in the queue. > That's not clear to me. The 2nd party doesn't know how the 3rd, 4th, 5th, etc. parties shuffled the outputs, since it doesn't have their decryption keys. --001a1135637e9080a90500380415 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Aug 9, 2014 at 6:10 AM, Sergio Lerner <se= rgiolerner@certimix.com> wrote:
=20 =20 =20
Hi Tim,
=C2=A0It's clear from the paper that the second party in the protoc= ol can de-anonymize the first party. So it's seems that dishonest shuffler= s would prefer to be in that position in the queue.

That's not clear to me. The= 2nd party doesn't know how the 3rd, 4th, 5th, etc. parties shuffled th= e outputs, since it doesn't have their decryption keys.
--001a1135637e9080a90500380415--