eosportal / eosportal-front Goto Github PK

If a user is using SSL we want the user to connect to a node supporting SSL.

My proposal:

Development Workflow

1. Create an issue or pick an available open issue.
2. Assign the issue to yourself.
3. In waffle (https://waffle.io/zrts/eosportal-front) move the issue to "In Progress".
4. Create a feature branch.
5. Do development.
6. Create a pull request for the issue.
7. Move the issue to "Review" in waffle.

Review Workflow

1. Pick an issue from waffle's "Review" column.
2. Review it with comments.
3. If accepted merge it. Else, if not accepted make comments and move it back to "In Progress".

There should be a “top level” / “blockchains level” page. This should list available EOSIO blockchains.

In order to get voters more informed

From Doc_Worm:
Aloha have been doing some great work on their bp research portal https://www.alohaeos.com/vote#validate I believe the majority of the community would like to see non compliant block producers made visible on voting portals. Have you thought about adding a compliance pass / fail for each bp on eosportal?

These can be sorted on uptime for public node, and then random.

We need to be sure that the amount of votes its calculated ok.

It would be great a README explaining how to setup the project to start developing (including API?)

• How many BPs are allowed
• How many BPs are connected ( producing or not )
• Booted Date
• Total Voters
• Voter Percentage
• Total blocks produced
• Chain health

When a user clicks on a block on the chain specific page, a page showing information about that specific block should be displayed.

Right now its a bit complicated, I would suggest to have different layout based in language.

when opening a link directly to a producer (or refreshing the page) the bp.json info is not displayed: for instance http://eosportal-front.herokuapp.com/chain/3/producers/mosquitometa ,

In order to make things easier for BPs, we could add a button vote, that will mark that BP as voted and will move user to producer lists in order to allow user to keep adding more votes.

hi looking at
http://eosportal.io/chain/12/producers
it shows eosromania22 in Greece
that's wrong, where is pulling that info from?

After validation from peers both locally and abroad, surfacing this here. Users on the technical end of the user funnel will have no problem reaching the point where they can vote leveraging the minimalistic front-end we have provided users.

However, those who find technology more challenging will almost certainly run into trouble. While these concerns are loosely covered in the 'Help' section of the website -- what I am proposing is that we go above and beyond, leveraging a design language which focuses on the side of the user funnel whom lack technical skills.

As evidenced by the thousands of issues surfaced by users attempting to configure and register EOS addresses during the EOS token registration process -- voting has a high likelihood to suffer the same fate.

As an action item, I would like to build out a mock-up (preferably in collaboration with others interested) of a user focused journey through the voting process, while laying a framework which will be simple for further UI development to take place as other pages / resources become necessary. Completely open to collaboration if the community decides this is worthy of the time.

Also happy to Merge Issue 35 and 36 into this effort.

I am a noob setting up Scatter in Chrome (so I can vote.) After following several videos and installing Scatter into Chrome, setting up the Key Pair, an Identity, and Pairing Scatter successfully, I clicked on the Voting Power tab and instead of seeing a list of available candidates (like most videos show), I see this text:
"Delegating Bandwidth"
"In order to vote you will need to delegate some of your tokens to yourself for CPU and Net. This will allow you to use those same staked tokens for voting as well."

Doing Google searches for How To delegate EOS token "bandwidth to yourself for CPU and Net", I can't seem to find anything. Any help is appreciated. Thanks.

When filtering producers by name and writing a filter that does not yield any producers, the input field is removed and this message is displayed: "This chain doesn't have any producers registered yet.".

How to reproduce: Go to the portal, select the chain you wish to interact with. Start typing a BP's identifier, and mistype the string so that no results would be found. System throws, and produces a message saying no blockchain is selected resulting in the user requiring to refresh the page.

Some numbers are hard to read

The chain specific page should have an info tab with Information about the chain.

Chains will have multiple endpoints, if user is using https (recommended) we should check and use one of the nodes that support https instead of the default one.

When a user clicks on a BP (active or candidate) on the chain specific page, a page showing information about that specific BP should be displayed.

It looks like your vote tally is incorrect. You don't include proxy votes correctly.
This looks more like it
https://www.alohaeos.com/vote?sort=vote_count&sortDir=asc

We need to allow users to read content in different languages

Hi,
I've created a voting authority by doing:
cleos set account permission ACCOUNT_NAME voting '{"threshold":1,"keys":[{"key":"PUBLIC_KEY","weight":1}]}' "active" -p ACCOUNT_NAME@active
And linked it to voteproducer action by doing:
cleos set action permission ACCOUNT_NAME eosio.system voteproducer voting -p ACCOUNT_NAME@active

The reason I did this is to enable me to use the voting portal without sharing my private key with Scatter.

Now after I've set up Scatter identity ACCOUNT_NAME@voting, and paired with the voting portal, I'm getting this error:

Voting failed: Missing required accounts, repull the identity

When I change my voting identity to ACCOUNT_NAME@active in Scatter, The portal takes me to the Scatter confirmation page but then fails to authenticate the transaction. (As it should, because I don't have the ACCOUNT_NAME@active private key in Scatter)
@nsjames

Allow delegate/undelegate using a slider/percentage of user's SYS/EOS tokens

Get BPs by API
That API should contain information from bp.json + information from chain.

API should get Location from bp.json

Order producers by last created block.

When a user clicks on a chain on the top-level page, a page showing information about that specific chain should be displayed.