I have had another idea. 😛
It would be very cool to be able to have TOR and I2P seeds. For example: I could run BT within TOR-land on a .onion address. A client could connect their BT to TOR and have it seed from a .onion address and use it as a connected peer. (Likewise for I2P: someone could run a .i2p service that is — well — BC).
I might setup a couple of nodes in this fashion and post the tunnels on this forum. I already run a lot of I2P and TOR nodes so adding BC to the mix is quite trivial.
I support the idea of making BC compatible with TOR and I2P to increase the privacy of the system. I mean: why re-invent the wheel? There are thousands of mix network nodes just sitting there that can be used to enhance BC. 🙂
I’ve been thinking about that for a while. I want to add the backend support for .onion addresses and connecting to them, then go from there.
There aren’t many .onion addresses in use for anything because the user has to go through a number of steps to create one. Configure TOR to generate a .onion address, restart TOR, configure it with the generated address. Perhaps this is intentional to keep TOR so it can’t be integrated into file sharing programs in any sufficiently automated way.
868 total views, 1 views todayhttps://bitcointalk.org/index.php?topic=22.msg113#msg113