Hi erverybody. New wallet release is approaching. We will be setting a break to the next version at block 125 000. Watch this thread closely in the next few days. Masternode payments will be significantly higher with this release. As before, anybody that has not updated once we reach 125 000, will be on a obsolete chain.
I also want to give everybody a heads up concerning planned changes to masternode payment distribution. These change will not be part of this update, but the next one after that:
1. Running several masternodes on the same IP under different ports will no longer be allowed - this does not benefit the network in any way. Masternodes will simply not be accepted onto the network if a similar node with the same IP is already present.
2. If there are many masternodes in a certain geographical area competing for payouts, these will receive less than a masternode which has less competition in it' area. It will also depend on the traffic. As we are planning to host services on the masternodes, we want the masternode network to be fast and responsive, with masternodes preferably being placed where they can benefit the network the most.
Yours, team swipp
While making masternodes meaningful is valuable, how will distance/proximity be determined? I can buy an MN in my basement and create 40 ms between it and the rest of the world and be rewarded because I appear to be far away from all of the other MNs.
Separately, forcing MNs to not share physical hosts is not a bad idea. It will penalize hosters like Vultr -- who, while they may be on different IPs, aren't necessarily going to be far from each other.
The logical resolution of this distance issue is that instead of using hosters, people will host MNs on their residential internet connections and universities ... which improves diversity at the sacrifice of resilience.
Fusion