This is my revised proposition.
I think the best solution is to have a constant poll, and decide dynamically the percentage of the anonymous and IPbased masternodes. And according to this voted percentage, new
masternodes (selected randomly) must be forced to become anonymous and other new
masternodes must be forced to behave as reverse proxies to the hidden network. The poll of course should be protected, decentralized and mirrored into all the anonymous section of the dash network.
It is very crucial to select randomly the IPbased and the anonymous new
masternodes (according to the result of the appropriate poll that is always active, so that we can change the percentage of anonymous and IPbased new
masternodes , according to the extend of the attack beeing made at the public dash network) because this randomness makes much more difficult the task of prohibiting the public dash network. The randomness can be calcutated using appropriate cryptographic protocols, among masternode owners.
mastenodes, as long as they are baptized and randomly taken their anonymous state, they can remain like that.
For example, lets suppose that the current result of this supposed permanent poll is the below:
Should we compel the core team to implement an anonymizing layer (i2p, tor etc)
- *Yes, all MNs anonymized 15 vote(s) 37.5%
- Yes, but MNOs choose IP based or anonymous 13 vote(s) 32.5%
- No, all MNs should run on public IPs 12 vote(s) 30.0%
So we should have 37.5% of anonymous nodes, 32.5% free to choose by the MNO, and 30% IPbased nodes. The IPbased and the anonymous nodes should be selected by the protocol randomly according to the current vote result, and the new arriving
lucky (or unlucky) MNOs should be forced (by the protocol) to respect the decision of the protocol.
I gave a solution above, so what about it? What do you think?