> 'kid'
If you want to have a flame war I'm not interested, resulting to name calling is not at all conducive to productive debates.
> I never said Your masternode alone.
No you did not say it. But when your argument is that the NSA will essentially control 99% of the masternodes, it is equivalent to only sending it through your own masternode.
> So you're wrong about it not being possible
I never said that. In fact I could have told you, and should have been more clear about this, that someone absolutely could choose whichever masternode they want. Once the protocol is open sourced as RC5, you can make it do whatever you want (that is compatible with the masternodes you are interacting with at least), that's the beauty of open source software!
What you have described in this specific post, is a good idea. But I need to be clear, the rest of the thread, and your arguing for free master nodes, are terrible ideas.
If you specify one masternode which you know is "safe", yes, it does make the protocol more secure. If you take the time to go read the discussion from many months ago when darksend was first being discussed you can see this was brought up. Making it a default option, however, only makes it confusing to users who don't have a masternode themselves and don't know anyone who does.
But what you described throughout the rest of this thread was very different from the very specific idea I just described.
You've been following darkcoin for 3 months and don't know where the 1k DRK goes? You are trying to argue for changing the protocol when you admit you don't understand fundamental aspects of it!
The developers don't make money from darksend, the 1k they cost never leaves your control, it is sent to an address you own to act as collateral, if you move it from that address, your masternode goes offline.
Finally, free vs paid masternodes. Remember when I said you didn't understand the technical implementations behind this? That was the part I was referring to. On a technical level, an implementation where every wallet was a masternode, as opposed to the current system, would not function. The idea to have masternodes cost money was done for many reasons.
As far as the networking issues I referred to, for the protocol to function each wallet client needs to maintain and keep updated a list of all the masternodes. To do this requires network traffic. At 1000 masternodes there is a reasonable amount of network traffic and memory usage.
But if there were 20,000,000 clients? It roughly may take 50 bytes to store the required information for each node, that is 1 gigabyte of RAM required just to keep track of the nodes. It also would require a consistent 1 megabyte per second internet connection to handle node discovery and updating. That is 86 gigabytes of data per day, which results in many users going through their entire monthly bandwidth cap in under a week. A mobile wallet would do it in under an hour.
There also is another issue with this. It is ddosable. Very easily and very cheaply ddosable. A large botnet could bring the network down and keep it down indefinitely and it wouldn't cost them a penny. Due to the prior issues I mentioned, memory requirements and network usage, by artificially inflating the size of the client list you could make it impossible for anything but very modern computers to run the daemon. Additionally, and here is the cruz of the problem, 10,000 nodes restarting a few times a minute could flood the network indefinitely, keeping the network nonfunctional for as long as the attacker wanted.
So please explain to me how there was not a single valid reason for masternodes to cost money again?
But since you want to hear from evan, here is a post by evan from very early in masternode development:
https://darkcointalk.org/threads/darkcoin-update-masternode-requirements-masternode-payments.225/
He explains both the feedback loop -> how even if the NSA wanted to, they simply could not buy 99% of the masternodes and the network issue and that too many masternodes is impractical on the network level.