Use Chainquery about block-explorer HOT 6 CLOSED

I am ready to take up the task, it could make the explorer much simpler and solve issues such as #8 or #31 that seem to be due to the block syncing process. As @tiger5226 suggested, there could be a direct DB connection to Chainquery.

from block-explorer.

I can setup the credentials for you. Ultimately, the block explorer is a great candidate to integrate with Chainquery. It was actually what I started from for Chainquery. So it should be a very close match on the schema. I would not expect many differences.

from block-explorer.

@marcdeb1 Testing credentials for Chainquery have been sent over. When we are ready to deploy we can setup a production account for the explorer.

from block-explorer.

The block explorer API is using different fields from Chainquery:

I would suggest to standardize the attributes and put the same as Chainquery (InputCount -> input_count), but since some people might use the API it could be a problem. What do you think ? Stay like before or change ?

from block-explorer.

It would be nice if we aligned across the organization. Chainquery schema in the standard now, so we should probably align on that. I think currently let's not break an api's but we should create an issue to address this with a long term solution that could include api versioning. Ultimately, block information should just come from chainquery api's. So we will probably want to deprecate the apis from the block explorer altogether. Block explorer should just be a pretty ui for chainquery data.

from block-explorer.

Solved with Chainquery integration

from block-explorer.