📅 Original date posted:2015-07-22
📝 Original message:I've thought about this as well, (in addition to making a java
implementation of the electrum server).
One solution would be for the client to combine all the addresses they are
interested in into a single bloom filter and send that to the server.
It would be pretty expensive for the server to check every address against
the bloom filter, but maybe for recent blocks (client can send how behind
they are) and for new transactions it wouldn't be bad at all.
The client could end up receiving a bunch of transactions they weren't
interested in but it would likely be manageable.
The client would also need to be fairly clever, including a set of static
ruse addresses and dynamic ruse addresses that they include in the filter.
That way a server would have a hard time using the bloom filter as a
fingerprint and figuring out which addresses are the real ones.
An alternative would be the server sending a bloom filter of addresses in
each block and then the client requesting entire blocks. This would use
more bandwidth, but it seems like it would be pretty simple to implement
and give good anonymity.
Basically the idea is to spend more bandwidth and CPU to keep the server in
the dark on what the client really wants.
On Wed, Jul 22, 2015 at 8:51 AM Thomas Voegtlin via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Hello,
>
> Although Electrum clients connect to several servers in order to fetch
> block headers, they typically request address balances and address
> histories from a single server. This means that the chosen server knows
> that a given set of addresses belong to the same wallet. That is true
> even if Electrum is used over TOR.
>
> There have been various proposals to improve on that, but none of them
> really convinced me so far. One recurrent proposal has been to create
> subsets of wallet addresses, and to send them to separate servers. In my
> opinion, this does not really improve anonymity, because it requires
> trusting more servers.
>
> 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
>
> What do you think? What are the costs and benefits of such an approach?
>
> (Note: this will not work if all servers, or a large fraction of them,
> are controlled by the same entity that controls M)
>
>
> Thomas
> _______________________________________________
> 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/20150722/0cc44782/attachment-0001.html>;
Joseph Gleason ⑈ [ARCHIVE] /
npub1qp…my8sw
2023-06-07 15:42:44
in reply to nevent1q…s2qf
Author Public Key
npub1qp59a7k7vxv0k8z277f50092ljk9mjg5du9lz8hlft37u4ggwqes5my8swPublished at
2023-06-07 15:42:44Event JSON
{
"id": "cf8f3ddbdc0e118fa6258c9994764b2d7fa4c17e9e949ec3b3d6c5b75cf5073e",
"pubkey": "00685efade6198fb1c4af79347bcaafcac5dc9146f0bf11eff4ae3ee55087033",
"created_at": 1686152564,
"kind": 1,
"tags": [
[
"e",
"118b9de54e189b18402c92d943ea538ff30d5f541b4aeaba9bb62ae15123b652",
"",
"root"
],
[
"e",
"978f3cd86db3f1e06c82f6b2746b5bc6a2b3d7a6ad16a0f0843502a02c5d2702",
"",
"reply"
],
[
"p",
"00685efade6198fb1c4af79347bcaafcac5dc9146f0bf11eff4ae3ee55087033"
]
],
"content": "📅 Original date posted:2015-07-22\n📝 Original message:I've thought about this as well, (in addition to making a java\nimplementation of the electrum server).\n\nOne solution would be for the client to combine all the addresses they are\ninterested in into a single bloom filter and send that to the server.\n\nIt would be pretty expensive for the server to check every address against\nthe bloom filter, but maybe for recent blocks (client can send how behind\nthey are) and for new transactions it wouldn't be bad at all.\n\nThe client could end up receiving a bunch of transactions they weren't\ninterested in but it would likely be manageable.\n\nThe client would also need to be fairly clever, including a set of static\nruse addresses and dynamic ruse addresses that they include in the filter.\nThat way a server would have a hard time using the bloom filter as a\nfingerprint and figuring out which addresses are the real ones.\n\nAn alternative would be the server sending a bloom filter of addresses in\neach block and then the client requesting entire blocks. This would use\nmore bandwidth, but it seems like it would be pretty simple to implement\nand give good anonymity.\n\nBasically the idea is to spend more bandwidth and CPU to keep the server in\nthe dark on what the client really wants.\n\nOn Wed, Jul 22, 2015 at 8:51 AM Thomas Voegtlin via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hello,\n\u003e\n\u003e Although Electrum clients connect to several servers in order to fetch\n\u003e block headers, they typically request address balances and address\n\u003e histories from a single server. This means that the chosen server knows\n\u003e that a given set of addresses belong to the same wallet. That is true\n\u003e even if Electrum is used over TOR.\n\u003e\n\u003e There have been various proposals to improve on that, but none of them\n\u003e really convinced me so far. One recurrent proposal has been to create\n\u003e subsets of wallet addresses, and to send them to separate servers. In my\n\u003e opinion, this does not really improve anonymity, because it requires\n\u003e trusting more servers.\n\u003e\n\u003e Here is an idea, inspired by TOR, on which I would like to have some\n\u003e feedback: We create an anonymous routing layer between Electrum servers\n\u003e and clients.\n\u003e\n\u003e * Each server S publishes a RSA public key, KS\n\u003e * Each client receives a list of available servers and their pubkeys\n\u003e * For each wallet address, addr_i, a client chooses a server S_i, and a\n\u003e RSA keypair (K_addr_i, k_addr_i)\n\u003e * The client creates a list of encrypted requests. Each request contains\n\u003e addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i\n\u003e * The client chooses a main server M, and sends the list of encrypted\n\u003e requests to M\n\u003e * M dispatches the client's requests to the corresponding servers S_i\n\u003e (without the client's IP address.)\n\u003e * Each server decrypts the requests it receives, performs the request,\n\u003e and encrypts the result with K_addr_i\n\u003e * M receives encrypted responses, and forwards them to the client.\n\u003e * The client decrypts the encrypted response with k_addr_i\n\u003e\n\u003e What do you think? What are the costs and benefits of such an approach?\n\u003e\n\u003e (Note: this will not work if all servers, or a large fraction of them,\n\u003e are controlled by the same entity that controls M)\n\u003e\n\u003e\n\u003e Thomas\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/20150722/0cc44782/attachment-0001.html\u003e",
"sig": "72581dffb086d85cde048339981129388b7b85241f414a8b92a3b24ea50eb8d18806dd9f4d349be76da705b247787566f3e033be8bf694f01696027fb0c4c613"
}