<div dir="ltr">This looks like a prime application for this PIR library: <a href="http://percy.sourceforge.net/apidocs/index.html">http://percy.sourceforge.net/apidocs/index.html</a></div><br><div class="gmail_quote"><div dir="ltr">Eric Voskuil via bitcoin-dev <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> schrieb am Do., 23. Juli 2015 um 02:07 Uhr:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is a good point. I didn't delve into the specifics of<br>
implementation due to the larger issues that I raised. Libbitcoin Server<br>
uses CurveZMQ, an implementation of CurveCP.<br>
<br>
<a href="http://curvecp.org" rel="noreferrer" target="_blank">http://curvecp.org</a><br>
<a href="http://curvezmq.org" rel="noreferrer" target="_blank">http://curvezmq.org</a><br>
<a href="https://en.bitcoin.it/wiki/Libbitcoin_Server" rel="noreferrer" target="_blank">https://en.bitcoin.it/wiki/Libbitcoin_Server</a><br>
<br>
e<br>
<br>
On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote:<br>
> Why RSA?<br>
><br>
>><br>
>> Here is an idea, inspired by TOR, on which I would like to have some<br>
>> feedback: We create an anonymous routing layer between Electrum servers<br>
>> and clients.<br>
>><br>
>> * Each server S publishes a RSA public key, KS<br>
>> * Each client receives a list of available servers and their pubkeys<br>
>> * For each wallet address, addr_i, a client chooses a server S_i, and a<br>
>> RSA keypair (K_addr_i, k_addr_i)<br>
>> * The client creates a list of encrypted requests. Each request contains<br>
>> addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i<br>
>> * The client chooses a main server M, and sends the list of encrypted<br>
>> requests to M<br>
>> * M dispatches the client's requests to the corresponding servers S_i<br>
>> (without the client's IP address.)<br>
>> * Each server decrypts the requests it receives, performs the request,<br>
>> and encrypts the result with K_addr_i<br>
>> * M receives encrypted responses, and forwards them to the client.<br>
>> * The client decrypts the encrypted response with k_addr_i<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>