sounds like DPOS without the 10 secs synchronization ... gonna read over it.. looks interesting
//edit: ui .. nice algorithm .. it seems each node has its own timer (randomly chosen) and whenever a timer goes to zero that nodes becomes the master node .. unless it received a message from the current master node .. then the counter is reset. I think it it a totally different problem .. It is more like having a master DPOS node and having multiple distributed nodes that serve as a entry point to the network maybe (just like a seed node) and the master node updates all the seed nodes .. once the master node fails .. one of the seed nodes takes over ..
IMHO this is more a backup procedure for a centralized consensus .. not the other way round ..
Still a nice find .. learn something new every day :-)
That is true but innovation can be found anywhere. Often people solve problems for you inadvertently while trying to do something else. I think whenever there is technical overlap there is potential for novel solutions to be found.
If we look at it as a pure algorithm maybe something within it is an improvement on DPoS.
In my opinion it's similar to DPoS in that DPoS does select a leader temporarily in the form of a delegate. 1 delegate is selected to verify a block, am I right? I will have to review this algorithm thoroughly and ask anyone else with a technical proclivity and spare time to do the same.