Scorum / how-to

Over the last few months the Scorum Delegate Voter got a few updates to increase the information available to delegates and users in support of their decision-making. Support is the name of the game. Link https://www.guiltyparties.com/scorum/ The tool is currently accessible from the main GP site. Information Displayed Delegate Name - The name of the operational delegate (block producer/witness). Current Votes - The total sum of staked investment (SP, processed calculation) of the delegate's supporters. Missed Blocks - The number of blocks the delegate missed while processing. Missed blocks happen for a variety of reasons and should not be seen as a dark mark against the delegate and its operator. When a block is missed by one delegate, the next delegate in line will process it. Version - The version of Scorum that the delegate is running. Once a delegate updates to a new version, the value displayed is changed once they process their first block on the new version. Created - Delegates created at the start of the blockchain with the value of 1970-01-01T00:00:00 are labeled as Founder. Delegates created at a later time have their respective account creation date listed. Link - This is the link that each delegate has the option of providing for more information about themselves. It is not necessary for operation and is informational. Activity - Delegates that are currently active and processing blocks are labeled as Processing (green background). Delegates that set their signing key to SCR1111111111111111111111111111111114T1Anm to indicate they wish to be taken out of the bock production rotation are labeled as Disabled (light gray background). Rank - Self-explanatory. Decision Making The aim of this tool is to make voting simple without inadvertently influencing decisions. It is up to each user to independently research the delegates they wish to support and to combine that research with the information provided on the page. For example, @vlad is a Founder (most already knew this), his server is upgraded to the latest version of 0.4.0 and he is actively processing blocks. @Bro-delegate was created in August 2018, currently links back to the profile of @ats-david for more information on who owns it (I'm the co-owner), has been upgraded to the latest version of 0.4.0 and is actively processing blocks. @Dgazek was created shortly after Scorum's launch in March 2018, has been upgraded to the latest version of 0.4.0 but is currently disabled. We don't know the reason why but the fact that he upgraded recently may indicate that he will re-enable it soon. @Tigra was created in April 2018, hasn't been upgraded since version 0.2.0 and is currently disabled. We can assume that his chances of being re-enabled soon if at all are lower than @dgazek's, since he's been disabled since 0.2.0, which is far longer. No delegate should be labeled as "good" or "bad" by anyone except for the individual voter (yourself). This is why the only color you see is the green Processing button. Green indicates normal operation in most cultures. The button for the Disabled is light gray versus red to indicate neutrality. Marking the Disabled as red would have negative connotations as red is the color of hazards/warnings in most cultures. You show your support with your votes and decide on your own. Delegates are not a political entity. We are all individuals or small teams of individuals who took our time to set up servers to process blocks and keep this blockchain running in a decentralized manner. Code All code is available on GitHub. It's as simple and as readable as possible. If you don't trust my site, run it on your own. Keys This page only uses your private key to sign the transaction locally. Private keys are never transmitted. You can download all the code and run locally if you prefer. There are more secure ways to vote, such as cli_wallet. Each time you vote you generate one transaction. Should you leave or reload the page, your Private Key will need to be re-inserted. It's not saved anywhere. Voting InstructionsEnter your account name and private key in the provided fields.Review the information line that indicates how many votes you have remaining (in yellow). There are 30 total.Click the check box at the front of each delegate's row. A checkmark will appear in the box. There are no other confirmations with the exception of the votes remaining number (in yellow) decreasing.All voted delegates will have a checkmark.To unvote a delegate, click the check box again and the checkmark will disappear. Information Only Instructions This tool can be used to check who's voting for who.Enter the name of the account you wish to check under Your Account Name but leave the Private Key blank. Click anywhere on the screen.You will see the number of votes remaining (in yellow) decrease if the account has voted for a delegate.The delegates the account has voted for will have checkmarks in their respective check boxes. Updates If you'd like to see additions to the tool or other similar components, let me know in the comments below.