Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a Discover delegates page to the delegates section #1828
Description of the problem
The DPOS system is an important part of Lisk. Forging delegates must be chosen carefully to ensure a stable and trustworthy blockchain.
Currently it's very difficult for most lisk owners to find out more information about active delegates and to decide which ones to vote for. Information is scattered across multiple sites, chat rooms and social websites. It's also hard for delegates to reach the many owners of lisk and share their campaign info.
Most lisk owners use the Lisk hub desktop wallet to access their lisk and perform transactions. This makes it the best place for adding a feature that allows people to discover delegates.
I suggest changing the Delegates section and adding a Discover delegates option as shown in the screenshot below.
Available sorting methods:
Delegate detail page:
After clicking on a delegate it will take the user to the Delegate details page. Which shows more information about the delegate. A personal message and perhaps additional statistics like vote weight, productivity or account age.
For a personal message to appear we must solve the following steps:
The current data field of 64 bytes is too small to provide enough info. My proposal is to let delegates send a transaction to their own account containing a specific code. Part of this code is a link to a simple text file hosted by the delegate or someone they trust.
This makes sure that if a server of a delegate hosting the text file becomes unreachable, it does not affect other delegates information. It's 'decentralized'.
The following code must be placed in the data field of a tx sent and received by the delegate:
64 bytes should be enough to hold the identifier, delegateInfo:, and the url to the text file.
A messaged can be changed by simply changing the text file on the server. Or by sending a new transaction with the identifier and pointing to a new address, since only the latest tx with the code is retrieved.
There are two steps to retrieve the message. When the Delegate details page is loaded, it makes an API call to a lisk node. The result of the call will contain a link to a textfile which is subsequently retrieved and shown to the users.
This following API call will retrieve the latest link to the delegate information textfile, other previously submitted identifiers are ignored.:
A message can be removed by deleting delegateInfo.txt from the server, resulting in a 'not found' error. Or by sending a new tx to their own account without a link
To make sure the delegate info is retrieved fast, save and looks good, certain specifications must be defined.
Implementing an easy method for voters to discover delegates will benefit the current lisk system and future sidechains.