eosportal / milestones

Milestones

All global tickets for the MVP and final product will live here.

What types of tickets?

Every ticket should be a singular functionality. All functionalities are welcome, and we will divide them into milestone markers.

---

Good Ticket: Allow users to filter BPs.

Bad Ticket: Allows users to filter BPs by location.

Keep the tickets broad, and fill out the sub-functionalities or parameters within the ticket itself.

---

milestones's Issues

Display warning when a user has voted in a centralized manner

We should not completely disallow users to vote for whatever BPs they choose, but a warning should be displayed if they vote for too many BPs within the same countries, showing them that they are harming the chain.

Voter/Platform/BP Perspective

In EOS Portal we will allow BP candidates to add attributes to their candidacy. These could be tangible things like hardware specifications (number of machines, network, ...) and scaling plans, as well as intangible things such as reasoning behind wanting to become a block producer, moral values as well as other campaign promises, … etc.

• Voter perspective

  • Identify other BPs / proxies of interest to look into
  • “Pair” with other voters that have the same compass and prioritization between sets of values as oneself
  • Find their individual places within communities in the community
  • Receive weighted notifications based on level of pairing with BPs, proxies and voters
  • In the case of a misbehaving BP or proxy we will know which voters to alert

• Platform perspective

  • Help voters to make it easier to engage with the community and verify that their votes actually help moving us in a direction that each individual voter see fit
  • Keep BPs / proxies honest
  • Give voters influence and the positive feelings that arises from being needed

• BP perspective

  • Marketing
  • Knowing how to address criticism

Multiple Chains

The portal should allow voting to occur on multiple chains so that we are agnostic to any single chain and not endorsing any effort.

Users should be able to select a chain and be able to see things such as

• chain_id
• total_voters - Accumulation of voters ( not votes )
• vote_percentage - Percentage of total funds voted to date
• boot_date - The date the chain itself was booted
• connected_bps - The number of BPs registered ( and connected ) to this chain

Randomise default list & add filters

As a Block Producing candidate, it would be nice to see the default list randomised versus having it in descending order of largest vote holders. This will improve fairness for all block producers. Additionally, filtering options can be implemented such as; geographical location, vote percentage, newest and oldest.

Allow users to view information about a BP

A user should be able to view information about a BP.

This should include:

• attributes added by the BP itself,
• votes,
• missed blocks (with a possible explanation from the BP)?

Allow users to vote/unvote for a list of BPs on a given chain

It needs to be clear to users that there is a 3 day time limit between unvoting and getting back tokens, and that undelegating BW causes a reduction in voting power

Video / Gif proof of life.

Users should be able to learn how to install and setup Scatter

Provide READMEs for repos so that anyone can raise portals

In order to get less friction from new contributors we should improve the readme with the steps to run the project in local

Migrate eosPHP to dawn4

https://github.com/kesar/eos-php may be required for backend to pull data from blockchain.

Allow accounts to delegate/undelegate Bandwidth

This is needed for users to be able to vote.
They should be able to see their total and select an amount from within it to use as voting power.