š
Original date posted:2014-08-07
š Original message: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 :(
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140807/4a1c63a5/attachment.sig>;
xor [ARCHIVE] /
npub14aā¦g6tv3
2023-06-07 15:24:52
in reply to nevent1qā¦0qhn
Author Public Key
npub14a7v3r4ppfy007s0tk2h0ujh38h9x4t6jyrndev9qmmazd2vrsvqxg6tv3Published at
2023-06-07 15:24:52Event JSON
{
"id": "1ec2b86983fdfa5c9089d0fadd1dfeaddf16d1a1b95af48dd23e0ccd73a4a171",
"pubkey": "af7cc88ea10a48f7fa0f5d9577f25789ee53557a910736e58506f7d1354c1c18",
"created_at": 1686151492,
"kind": 1,
"tags": [
[
"e",
"a942c80dc37c447bacddc612a33c90a81e1b3e70d811ef9f0fc4da5a1e2d27ad",
"",
"root"
],
[
"e",
"0dc0071f018799ac10b5a2961c47c0ef3721f4cc6a8616db241fc4d6446d7231",
"",
"reply"
],
[
"p",
"c6d7a400897460d9a2c07bbad58731b6d04267edd75af42af45f471b04581ec2"
]
],
"content": "š
Original date posted:2014-08-07\nš Original message:On Thursday, August 07, 2014 12:22:31 AM Tim Ruffing wrote:\n\u003e - Decentralization / no third party:\n\u003e There is no (trusted or untrusted) third party in a run of the protocol.\n\u003e (Still, as in all mixing solutions, users need some way to gather together\n\u003e before they can run the protocol. This can be done via a P2P protocol if a\n\u003e decentralized solution is desired also for this step.)\n[...]\n\u003e http://crypsys.mmci.uni-saarland.de/projects/CoinShuffle/ for a technical\n\u003e overview. \n\nI think the description at your website leaves out the truly interesting part:\nHow do you decentralize this securely?\n- How do Alice, Bob, Charlie and Dave communicate, i.e. which network is used \nfor communication and how?\n- How does Alice know that Bob, Charlie and Dave are not the same person?\n(= how do you prevent a Sybil attack?)\n\nBecause thats the real problem with mixing it seems - ensuring that your \nmixing partners are actually 100 people and not just 1 attacker. There are \nprobably many mixing algorithms which work if you solve that problem, but I \ndon't see how you offer a solution for it :(\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 836 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140807/4a1c63a5/attachment.sig\u003e",
"sig": "bdd5ecc89fa5f16a27a9da4f4d18af827eebf43ff4bb032e497cb75558a0062cdcdf0fd0ca57d4aa59ec5251cef32bed0cb200033d774c650059af5fdcb44f08"
}