Message-ID: <55B03032.5020306@voskuil.org>
Date: Wed, 22 Jul 2015 17:07:14 -0700
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: gb <kiwigb@yahoo.com>, Thomas Voegtlin <thomasv@electrum.org>
References: <55AFBBE6.3060702@electrum.org> <1437606706.2688.0.camel@yahoo.com>
In-Reply-To: <1437606706.2688.0.camel@yahoo.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA"
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Making Electrum more anonymous
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This is a good point. I didn't delve into the specifics of
implementation due to the larger issues that I raised. Libbitcoin Server
uses CurveZMQ, an implementation of CurveCP.

http://curvecp.org
http://curvezmq.org
https://en.bitcoin.it/wiki/Libbitcoin_Server

e

On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote:
> Why RSA?
>=20
>>
>> Here is an idea, inspired by TOR, on which I would like to have some
>> feedback: We create an anonymous routing layer between Electrum server=
s
>> and clients.
>>
>> * Each server S publishes a RSA public key, KS
>> * Each client receives a list of available servers and their pubkeys
>> * For each wallet address, addr_i, a client chooses a server S_i, and =
a
>> RSA keypair (K_addr_i, k_addr_i)
>> * The client creates a list of encrypted requests. Each request contai=
ns
>> addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i
>> * The client chooses a main server M, and sends the list of encrypted
>> requests to M
>> * M dispatches the client's requests to the corresponding servers S_i
>> (without the client's IP address.)
>> * Each server decrypts the requests it receives, performs the request,=

>> and encrypts the result with K_addr_i
>> * M receives encrypted responses, and forwards them to the client.
>> * The client decrypts the encrypted response with k_addr_i


--6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVsDAzAAoJEDzYwH8LXOFOoWQH/3rKskYOpSeihm9lP42pDwkX
gJtrVawkwCco5YFhm8E68V9JowXlmajJDeaH+P1Y6ma/Lhq4IBer2tUI+/Sr9KEp
Liwa4TvqEcjAW8wR9frRGIQgxeuJKntFRGSIi5qrDpsJI2eHZCRgWG/hWx7op0I/
K7wZa4OtwfRaVDFFkFH/af9qeFr3oiKiqhdUO6O9zUf7USLb811oxD0JEQtdeG1c
7hqZT0GmU2MSzpd9yPS8se+ob9PvK6VGeHxq7z9McBY8ZqccqhkBQ6sjQBtHn8z3
lBWFudqKRXIHGU/Hw6yx+MY/rA6eNYdwpNQuqF1cW71pAi82g/ss4D7jvWQ7960=
=ooug
-----END PGP SIGNATURE-----

--6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA--