eosportal / eosportal-api Goto Github PK

Hello.
I have run application locally, but without database migration it is not possible to do anything.

Can you upload database snapshot or migration script?

It will be common for nodes and chains to go down and they should be remove from the reference.

Right now the front-end has to traverse the array of nodes to find an available network each time.
The front end can notify the backend of fallen nodes but it might get notified multiple times by many users at once.

https://github.com/EOSPortal/eosportal-front/blob/master/src/views/Chain.vue#L88

We will need and endpoint where chains can be submitted.

This endpoint will try to validate that chain has a valid /v1/chain/get_info & pull information (total_voters, connected_bps)

If chain has same chain_id, we will add it to possible nodes to connect. We will need to create a list of nodes.

Any limitation to avoid spam? IP related perhaps?

For filtering and ordering purposes the chains should come back with a few properties:

• 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

Using https://github.com/kesar/eos-php

What do we need to store? I dont know what the old import script was doing.

From what I imagine, we may need to count blocks produced iterating using:

$block = $client->chain()->getBlock($blockNumber);

We could need to store actions that happens in Eric's contract for easy access?

$actions = $client->history()->getActions('eric.contract');

Anything else?

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

Please include instructions on setting up and running project locally for new developers who want to join and contribute to the project.