Quote from: Broesel on April 16, 2018, 09:17:14 AM

Quote from: damberg on April 16, 2018, 09:04:48 AM

Quote from: Broesel on April 16, 2018, 07:52:06 AM

Well, i agree. It was not the good way to go and just do the changes without a vote (especially when claiming 100% governance). ANY IMPORTANT changes to the system must go through a vote now IMO. Otherwise you get the problems, we got now with angry miners and confused MN owners regarding updates and downtimes of their MNs, which leads to uncertainty and stress that could have been avoided.

I will oppose you in this case. A chainsplit is a very specific emergency situation which requires immediate and decisive action. In my opinion, team followed through correctly, they took all necessary steps to clear the situation and make the blockchain run. Voting would probably lead to delayed solution, further continuation of splitted chains, losses for miners and even bigger disappointment among MN holders.

It has been hard time for ALQO but it remains strong. Another voting after the dust settles is a great decision.

Before the update there was no chainsplit and i am not quite sure why they had to release the update as fast as they did. They did remove the zerocoin protcoll from the update befor releasing it, but they could have done the vote before the update or am I wrong there?

Another topic: the newly released alqo-qt.exe https://github.com/ALQOCRYPTO/ALQO/releases/ is not syncing with the blockchain.The block explorer is also under maintainance and i have no idea if my MN is running. This is very annoying.

edit: new qt.exe is syncing now, after i deleted everything except: qt.exe, wallet.da and masternode.conf and restarted.

The update that changed payout structure (in favour of MN holders) was released as a response to strong bearish pressure on price (some other reasons also applied). Theoretically, you are right, there could have been voting before the original update.

This is standard situation after sidechain/splitchain attempts. Official pool will eventually fix the original blockchain, and explorer will be refreshed. You can check the deamon if your MN is running. It could have been much worse ..