š
Original date posted:2015-07-22
š Original message: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
>
gb [ARCHIVE] /
npub1j0ā¦u0kje
2023-06-07 15:42:45
in reply to nevent1qā¦7hvl
Author Public Key
npub1j0cee8lvw7v75c0vfsgfpt5xv8qmr3xzhlwpg9lestngmzwu0u9s6u0kjePublished at
2023-06-07 15:42:45Event JSON
{
"id": "b9e96e2a33817487e33c1b8f820450c22c4217af372e6834c050fb34f21634cf",
"pubkey": "93f19c9fec7799ea61ec4c1090ae8661c1b1c4c2bfdc1417f982e68d89dc7f0b",
"created_at": 1686152565,
"kind": 1,
"tags": [
[
"e",
"118b9de54e189b18402c92d943ea538ff30d5f541b4aeaba9bb62ae15123b652",
"",
"root"
],
[
"e",
"8261569ee3d6b8cdd795487ab16eb3f57e6cb74f0bfc0750336494ce87678455",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "š
Original date posted:2015-07-22\nš Original message:Why RSA?\n\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",
"sig": "2f12c06c64c7baa522ea0702e3293cf9f3f92d19fb952359c8965bf409b015ddb1fea5aea4b7538c187f1c1e602f29c766b03d0bbb86676acb12348fe947d8e3"
}