We had the diff talks a couple of times now and: NO it's not broken. It's exactly how diff retarget works. The issue is not the network the issue is 1 guy that directs hash in a smart way. He puts hash on when the diff is low cause blocks will come in fast to correct the delay we had, once we solved 30 blocks he will point the hash elsewhere and leaves us with high diff. Once we solved another 30 blocks he comes back. That's not a broken algo, that's being smart. We have seen this in the past on so many coins. Multipool has killed so many coins by doing this.
If we change the diff retarget, he will hop on and off in shorter time spans. That doesn't really solve the problem. I don't really get why we have so many discussions about it. If you want to understand how diff works read:
https://en.bitcoin.it/wiki/DifficultyThere are also a couple of good topics on stackoverflow. I get why everyone is crying but this won't solve the problem. VIVO is profitable to mine and the hash is currently low. So it's easy to play. As the project grows and the hash rate this will become harder to do. If you have been around in the last years you will have seen this before. It's annoying yes but it ain't a bug.
There is no guarantee that we will solve 720 blocks a day, it is not a fixed rule. The outcome should be predictable but it isn't. Even with shorter diff changes, i can still fuck the network when the real hash is 2ghs and I throw 20ghs on it. What will you do then? Cap on ghs per miner? Cause it ain't working like you want it?
So please, before flooding all channels about the diff, go out have a read, learn how it works and try to understand what is happening.