Quote from: Litoshi on April 26, 2015, 06:59:09 PM

Quote from: imd1 on April 26, 2015, 03:39:01 PM

Quote from: Passion_ltc on April 26, 2015, 10:59:47 AM

Quote from: imd1 on April 26, 2015, 09:48:45 AM

Also in the 'Delegate Monitor' page, is there a way to identify which of the delegates belong to the initial 101 setup to start off DPOS and which are the ones setup later by community or devs ?

Mal made a list of all initial 101 delegates. You can find it here: http://forum.crypti.me/viewtopic.php?f=17&t=42

Would be cool, if you set up a delegate. We need more from the community.

Thanks for list of 101 delegates.

I remember reading that the initial 101 delegates would always be there as a failover/fallback delegate even if none of these were among the 101 forging delegates at the time.

If this is the case, was wondering whether it would be useful to have some sort of marking to identify/differentiate these delegates on the 'Delegate Monitor' page ?

am not sure what kind of marking you are asking for. The top 101 delegates will always be able to forge, IF THEY HAVE FORGING ENABLED. If a 101 club delegate stopped forging, they would still be in the top unless they were voted down. There is no present way to delete a delegate or to move a standby into the 101 club other than by votes.

It would be more expeditious if a delegate were to be bumped out of the top 101 for having X number of blocks in a row fail to forge, or if uptime fell below a certain number. But that is not in the code right now.

Presently, votes control everything.

Suggestions:

1. Implement a system to replace poor performing Top Delegates with top-voted Standby Delegates if Top Delegate performance falls below pre-set minimum performance limits.

2. The list of the original 101 Foundation delegates needs to be hard-coded in 0.2.1 client code. Anytime there is a click on the "Delegates" link in the Client, the resulting list of Top Delegates and Standby Delegates can be color coded by reference to this list on whether or not they are Original Foundation Delegates.

3. Another column needs to be added with a "Current Consecutive Missed Cycles" (CCMC) statistic for each Delegate to go along with their "uptime". A 101 Club Delegate could leave the system permanently without notice and his uptime would degrade only very slowly. It might take weeks or even months for his uptime statistic getting bad enough to alert users of the need to downvote him. However, such a vanished Forging Delegate would have a sky-high CCMC score of 85 after only 24 hours.

4. The current Top Delegate sort is by popularity, not performance. This is backwards. The Top Delegate sort needs to be by uptime or preferably CCMC, not votes. Poor-performing delegates should be in the position of highest visibility at the top of the list, perhaps color coded red if their uptime / CCMC scores fall below a minimum desirable threshold. A Lite Wallet user should not have to search all 101 delegates looking for poor uptimes scattered occasionally among mostly high uptime figures.

5. I still think we should rebrand the "Crypti Lite" software as "Crypti Wallet", and the current "Crypti" software as "Crypti Delegate" or "Crypti Node".

I'm gonna cross-post these suggestions over in the Suggestion Box on the other forum.