That settles it for me then, I told myself if I get any support at all even one person I will put the effort in to try to save this coin and resurrect the true intentions of what this project was all about. I know it needs 51% attack support first or no real exchange, such as Cryptopia will feel safe listing it, the whole tribal thing is going to have to be addressed tenderly, and in a way that could work, the direct route obviously has failed, but maybe some creative ideas would help, fundraisers or charity events highlighting the tribe and what they have been through, and how this coin can help for instance is just one idea that is possible and feasible. I will give Payu or any other Maza dev a chance to step up and give a roadmap or a direction for the coin, if nothing is heard from Payu or any dev once LCC releases the worker bee's after their testnet is a success, I will immediately fork the coin adding the 51% attack protection. Until then, I will watch and wait, and will prepare a new website and new announcement and new white paper with a roadmap. This can all be contributed through Maza volunteers @ GitHub and on Bitcointalk for ideas and to help with the relaunch. Stay in touch, PM with your own support. I am open to any suggestions this community can offer. Waiting and watching until further notice.

You have my support in being proactive here. I'm not a fan of Masternodes which the current dev wants to add. I imagine it will take months and by that time it's likely that Cryptopia will delist. In addition, in my experience Masternodes need a lot more dev support than Maza has, since it's much more likely that nodes will fork due to Masternode synchronization issues. I've seen this happen in a least a few coins already. There are other paths to attack protection such as what you suggest, I fear that Masternodes will just create a class system in Maza which will not be beneficial at all.