3 ms·
Here's a question I have on this -- I've been eagerly awaiting the new functionality to have onion addresses where using them doesn't reveal their existence. So
by zaroth 9y ago
Here's a question I have on this -- I've been eagerly awaiting the new functionality to have onion addresses where using them doesn't reveal their existence. So the address itself becomes a form of shared key.
But this opens another possibility of one-time addresses, and address scalability. My question is, does network cost increase with number of addresses? If peers on the network are using one-time addresses to form circuits, will that scale fine?
Basically I am envisioning two people communicating via dedicated addresses for their own use only. So a single key becomes a network channel to send data to a specific peer. That "peer" could actually be many different devices, but all ultimately connect to the same distributed application with a shared state.
So basically onion addresses are usernames which also let you pipe data to that user, right? How is this not the coolest thing ever?
- asn_tor 9y agoEach onion service does increase network load but not anything super intense. The use case you suggested should be possible. Also check out ricochet which works with legacy onions for chat.