XSN-Core Update | MN Challenge Requirements

Rather than see-saw our core team decided it best to implement masternode challenge requirements (sending masternodes a challenge to solve in under a certain amount of time, if they exceed challenge runtime often it will result in a ban). This can be raised to lower MN’s (increase staking) and lowered to raise the number of MN’s (decrease staking). All masternodes would need to update together…There are a few working models currently we can go off of to ensure stability. We don’t believe this challenge runtime would need to be updated often, maybe once a year or even longer if at all. The idea is yes MN’s would need to upgrade the specs — however this would allow many more responsibilities we can give to the masternodes + key features in our roadmap (for example cross chain proof of stake, light atomic swaps, TOR implementation on the MN network would be services provided by masternodes) These may need to be a minimum level of power to handle heavy traffic as we believe these will be very popular features.

In order to compensate the Mn’s for this extra power we have the option of implementing fees on the user when they use these given features which go to the Mn’s providing the service. If masternode owners believe this feature will be popular than it is well worth it to upgrade as the long term ROI will be much higher. In addition TPoS will result in the entire network being more secure than tradition POS as cold storage and offline wallets will be constantly staking + adding extra active pos security to the network, putting less importance on needing active stakers at a given time.

Stay up to date on XSN news, announcements, and more via our discord https://discord.gg/NVxdxCr