📅 Original date posted:2015-07-23
📝 Original message:This looks like a prime application for this PIR library:
http://percy.sourceforge.net/apidocs/index.html
Eric Voskuil via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org>
schrieb am Do., 23. Juli 2015 um 02:07 Uhr:
> 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?
> >
> >>
> >> Here is an idea, inspired by TOR, on which I would like to have some
> >> feedback: We create an anonymous routing layer between Electrum servers
> >> 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 contains
> >> 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
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/63b8773b/attachment.html>;
Stefan Richter [ARCHIVE] /
npub19f…f4wf0
2023-06-07 15:42:46
in reply to nevent1q…fvl9
Author Public Key
npub19fnl48y9j4fk9w0a284mqvszq6fuppelqp2tcxf0s37l95avdtussf4wf0Published at
2023-06-07 15:42:46Event JSON
{
"id": "5e7d5ecb49a2fe7fc3b6f7608fc3473e8176ac63579c83736615c2576e45f0ef",
"pubkey": "2a67fa9c85955362b9fd51ebb032020693c0873f0054bc192f847df2d3ac6af9",
"created_at": 1686152566,
"kind": 1,
"tags": [
[
"e",
"118b9de54e189b18402c92d943ea538ff30d5f541b4aeaba9bb62ae15123b652",
"",
"root"
],
[
"e",
"f61a77fc0be55d6fb4d9d921bbd38f2b4241a82f6d2b75e6ffff68c852e3ec27",
"",
"reply"
],
[
"p",
"d1e5e343064328be063c36deb0dacb660b8589dcbca90112f9c449503b63ebba"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:This looks like a prime application for this PIR library:\nhttp://percy.sourceforge.net/apidocs/index.html\n\nEric Voskuil via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\nschrieb am Do., 23. Juli 2015 um 02:07 Uhr:\n\n\u003e This is a good point. I didn't delve into the specifics of\n\u003e implementation due to the larger issues that I raised. Libbitcoin Server\n\u003e uses CurveZMQ, an implementation of CurveCP.\n\u003e\n\u003e http://curvecp.org\n\u003e http://curvezmq.org\n\u003e https://en.bitcoin.it/wiki/Libbitcoin_Server\n\u003e\n\u003e e\n\u003e\n\u003e On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote:\n\u003e \u003e Why RSA?\n\u003e \u003e\n\u003e \u003e\u003e\n\u003e \u003e\u003e Here is an idea, inspired by TOR, on which I would like to have some\n\u003e \u003e\u003e feedback: We create an anonymous routing layer between Electrum servers\n\u003e \u003e\u003e and clients.\n\u003e \u003e\u003e\n\u003e \u003e\u003e * Each server S publishes a RSA public key, KS\n\u003e \u003e\u003e * Each client receives a list of available servers and their pubkeys\n\u003e \u003e\u003e * For each wallet address, addr_i, a client chooses a server S_i, and a\n\u003e \u003e\u003e RSA keypair (K_addr_i, k_addr_i)\n\u003e \u003e\u003e * The client creates a list of encrypted requests. Each request contains\n\u003e \u003e\u003e addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i\n\u003e \u003e\u003e * The client chooses a main server M, and sends the list of encrypted\n\u003e \u003e\u003e requests to M\n\u003e \u003e\u003e * M dispatches the client's requests to the corresponding servers S_i\n\u003e \u003e\u003e (without the client's IP address.)\n\u003e \u003e\u003e * Each server decrypts the requests it receives, performs the request,\n\u003e \u003e\u003e and encrypts the result with K_addr_i\n\u003e \u003e\u003e * M receives encrypted responses, and forwards them to the client.\n\u003e \u003e\u003e * The client decrypts the encrypted response with k_addr_i\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/63b8773b/attachment.html\u003e",
"sig": "3fbe815fd549b84a3f7f4b04707b1eaef2ed8d6c602b4a1258ae4347e88de3e0bc18974548b5b97326fb28639a5308252bfe5b44e10ae5de07d4bbd4bc4c9a39"
}