Hey guys, I'm looking into integrating TOR network into CACHeCoin. The idea is, by default, the coin should connect through the tor network, with the option of disabling it and connecting normally. This will help boost some anonymity within the coin and help the TOR network by keeping up the nodes :-) The idea is, if the person activated connection through tor (which is already by default) he'll be able to receive stake. If he disables, No stake will be generated. Unfortunately i don't have much free time to dig into the tor code, but will be happy to receive the pull request on github https://github.com/kalgecin/CACHeCoin/ Please let me know what you think
well, after searching through your github, I realized you have not even started anything on tor. I could give you a hand. I understand the protocol very well and have implemented my own version of it.
Certainly more useful than using Tor would be to use zero knowledge proofs (zerocoin) in your coin.
"help the TOR network by keeping up the nodes" That would require the nodes to be stable (run for multiple days without stop) relay nodes that contribute bandwith. This is not what a typical Tor client does and probably not something for desktop computers.
To integrate Tor without it being a relay you can run a Tor client and configure your coin client to use a socks proxy 127.0.0.1:9050
But really if you want a more anonymous coin you should go zerocoin style.
Good luck.
On 21/03/14 11:59, kalgecin wrote:
Hey guys, I'm looking into integrating TOR network into CACHeCoin. The idea is, by default, the coin should connect through the tor network, with the option of disabling it and connecting normally. This will help boost some anonymity within the coin and help the TOR network by keeping up the nodes :-) The idea is, if the person activated connection through tor (which is already by default) he'll be able to receive stake. If he disables, No stake will be generated. Unfortunately i don't have much free time to dig into the tor code, but will be happy to receive the pull request on github https://github.com/kalgecin/CACHeCoin/ Please let me know what you think
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
There are many users who keep their wallets up almost 24/7 for staking. And as long as they're on tor network, they can stake. That's the incentive to keep them on. I'm aware of the ability to use proxy, but it'd be much better if the proxy was already integrated into the wallet itself, and active by default
On Fri, Mar 21, 2014 at 4:43 PM, Rémi remi.py@yandex.com wrote:
Certainly more useful than using Tor would be to use zero knowledge proofs (zerocoin) in your coin.
"help the TOR network by keeping up the nodes" That would require the nodes to be stable (run for multiple days without stop) relay nodes that contribute bandwith. This is not what a typical Tor client does and probably not something for desktop computers.
To integrate Tor without it being a relay you can run a Tor client and configure your coin client to use a socks proxy 127.0.0.1:9050
But really if you want a more anonymous coin you should go zerocoin style.
Good luck.
On 21/03/14 11:59, kalgecin wrote:
Hey guys, I'm looking into integrating TOR network into CACHeCoin. The
idea
is, by default, the coin should connect through the tor network, with the option of disabling it and connecting normally. This will help boost some anonymity within the coin and help the TOR network by keeping up the
nodes
:-) The idea is, if the person activated connection through tor (which is already by default) he'll be able to receive stake. If he disables, No stake will be generated. Unfortunately i don't have much free time to dig into the tor code, but will be happy to receive the pull request on
github
https://github.com/kalgecin/CACHeCoin/ Please let me know what you think
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-
Frank Young -
kalgecin -
Rémi