Utilizing the Masternode network - DarkTor
One of the future goals is to turn the masternode network into a decentralized business for masternode operators. To do this we’ll add features that improve the privacy of end users and compete with centralized businesses. Our first endeavor into this is to make a completely private tor network within Darkcoin.
The Darkcoin network will begin to offer anonymous internet access via the masternode network. As a user, all you’ll have to do is pay a fee for 24 hours of access. This fee will be paid to a masternode in much the same way the masternode fees are paid, using a deterministic algorithm for distributing the payments evenly across the whole network.
There’s a few benefits to running a private tor network through Darkcoin.
Sybil resistant - Due to the cost of obtaining masternodes, it will be very difficult for any one person to view all traffic.
Anonymous Payments - Users can pay anonymously for the service
Private Network - Our tor network will be internal to darkcoin only. All traffic will be paid traffic, so the cost of running the service should be profitable for the masternode operators.
Faster than tor - Tor has historically been very slow. This will be a lean version, that has much higher throughput.
As for the cost of the service we’re thinking $0.50 per day or something to that effect.
We’re still working on the details how this will function and this isn’t a feature that we’re absolutely set on. We’re very interested to get the community’s response to see if it’s viable .
Other Future Ideas
Maybe after it’s opensource other developers can help with some of these ideas:
https://darkcointalk.org/threads/list-of-future-development-ideas.89/
I have seen a similar proposal on Bitcointalk
Would it be similar in implementation to this thread or something different.
Using the mini-blockchain for decentralized DNS and encrypted internet layer
https://bitcointalksearch.org/topic/m.8433997
Steps for establishing secure communication channel with a server:
1) client uses account tree to lookup IP of a domain
2) client sends hello message containing own public key to server
3) server signs the clients public key and sends it back
4) client reconstructs full public key of server from signed message and:
a) ensures the public key hash matches value in account tree
b) ensures the response is signed by that public key
c) ensures contents of response is their own public key