For reference, I found a discussion between myself and AnonyMint. For those that know him, I dont need to tell you about AnonyMint. For those that dont, he is brutally honest, very smart and obsessive about anonymity. He worries about stuff like future Quantum Computers cracking all current day encryptions!
So, this thread gives some insight into where I was several months ago:
https://bt.irlbtc.com/view/470987.msg5581647#msg5581647Now many of the design details have changed, some thanks to AnonyMint's feedback. As he says the key is being able to trust your privacyServer. Everything revolves around this, so for the truly paranoid, the solution is to setup your own privacyServer. If you cant trust yourself, then who can you trust?
I suggest that people that want to setup privacyServers for the public to use to start preparing now. People will want to know you, to be able to trust you as their privacyServer provider. I will make it so that privacyServer nodes get a percentage of the business that flows through them, eg. InstantDEX commissions. You will also earn nodecoins just for running a node. The privacyServers will eventually need Ddos protection, decent bandwidth, enough RAM. Not sure of the exact specs, but considering the hardware BTCD community put together to get 3 petahashes(!!), I dont see a big problem in getting enough privacyServers setup.
So, it will be a hub and spoke topology and we need to get more hubs than DRK has masternodes. However, just having nodes is not enough, we need to have each hub have at least 10 active users, otherwise attackers can use timing and knapsack analysis to deanonynimize.
I am envisioning the privacyServer providing many services, for example I already have a squid http/https proxy automatic install script. This allows you to get subscribers for http proxy service, which runs about $5 per month. Probably best to charge less to get more customers.
James
James, I will want to test/host a couple of privacyServers on a vps. Just let me know.
OK, for now you can clone
https://github.com/jl777/pNXT and make sure you can get it to compile
I hope to get the basic comms working soon and it would help if somebody else can also test
Thanks!
James, I'm happy to put up a privacyServer. I have access to either dedicated servers or VPS's (I'll use the latter to begin with) and can put DDOS protection in front. On the trust front, other than my profile here, I'm the co-founder of CryptoThrift, which is registered with ASIC in Australia so my credentials are publicly available. Other than compiling it, is there anything else you want me to do at this stage? do you need the node IP or do they self register with the network? Might be a good idea to get an IRC channel going aside from #bitcoindark so we can work through testing issues?
I prefer to use this thread for comms. The community should see all the stuff going on. You never know when someone lurking has the answer that can help. That is the power of decentralization!
Anyway, you have to convince the community, not me.
Some people have reported difficulty compiling, so if we can get foolproof instructions on how to compile it, that would be nice.
Also, I am rapid developing the master branch without regard to stability now, so no guarantees of what state the version you make is in. If it loads, that is good enough for now
This is a full cryptonote fork + my encrypted network overlay injected into it. All the nodes connect via p2p network, but each user needs to specifically choose a privacy server to use.
James
