From: xor <xor@freenetproject•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] CoinShuffle: decentralized CoinJoin without trusted third parties
Date: Thu, 07 Aug 2014 15:00:11 +0200 [thread overview]
Message-ID: <1530801.palqu9XdN4@1337h4x0r> (raw)
In-Reply-To: <8137823.B0x87S28xY@calzone>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
On Thursday, August 07, 2014 12:22:31 AM Tim Ruffing wrote:
> - Decentralization / no third party:
> There is no (trusted or untrusted) third party in a run of the protocol.
> (Still, as in all mixing solutions, users need some way to gather together
> before they can run the protocol. This can be done via a P2P protocol if a
> decentralized solution is desired also for this step.)
[...]
> http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/ for a technical
> overview.
I think the description at your website leaves out the truly interesting part:
How do you decentralize this securely?
- How do Alice, Bob, Charlie and Dave communicate, i.e. which network is used
for communication and how?
- How does Alice know that Bob, Charlie and Dave are not the same person?
(= how do you prevent a Sybil attack?)
Because thats the real problem with mixing it seems - ensuring that your
mixing partners are actually 100 people and not just 1 attacker. There are
probably many mixing algorithms which work if you solve that problem, but I
don't see how you offer a solution for it :(
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-07 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 22:22 Tim Ruffing
2014-08-07 13:00 ` xor [this message]
2014-08-09 10:04 ` Tim Ruffing
2014-08-09 13:10 ` Sergio Lerner
2014-08-09 20:17 ` Mark Friedenbach
2014-08-11 6:25 ` Chris Pacia
2014-08-11 6:30 ` Chris Pacia
2014-08-11 11:38 ` Tim Ruffing
2014-08-11 12:08 ` Mike Hearn
2014-08-11 17:06 ` Mark Friedenbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1530801.palqu9XdN4@1337h4x0r \
--to=xor@freenetproject$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox