Anyone who has followed EOS over the past few months is aware of the problems with the history APIs. The legacy plugin originally provided by B1 is deprecated and running it in full mode has been a nightmare for the few BPS that still provide it.
One solution provided by greymass team is the light history api. It provides history for the last n transactions for every account. This way you can cover 99% of the use cases.
For anyone interested in learning more about the importance of having nodes with history API I recommend listening to the EOS Aurora podcast with team greymass as guests, where this topic is discussed extensively.
There are other solutions to this problem although they all have their pros and cons:
- On the one hand we have proprietary and closed solutions such as the amazing dfuse of EOSCanada. A brilliant technical solution but with problems that leads to being tied to a single provider whose software is closed source. AKA vendor lock-in.
- On the other hand there is the v2 hyperion published by EOS Rio. It is an open and very complete solution, that anyone can implement. The only complaint is that it is a solution entirely developed by EOS Rio and has not come from the community consensus, although this could change in the future if more BPs adopt it as a standard.
We are aware of this problem, and as BP whose main asset is the infrastructure we are providing 2 nodes behind a load balancer implement the v1 light history api by greymass team to give service to all the apps that still rely on this version of the API.
At the time of publishing this article, these are the BPSs that offer this service:
Recently we are proud to announce our new tool for getting curated lists of all API, P2P and History Nodes for EOS Mainnet and other Chains. https://tools.eosmetal.io/nodestatus
With this tool, you can get a list of all BP Nodes and the status of their public services.
Our tool, checks every 30 mins all public information of the standard bp.json for each BP, and shows all Public End Point nodes connection status.
In addition, we are establishing the proper infrastructure to offer the hyperion v2 API and any other solution that may be developed in the future.
We are committed to providing the necessary infrastructure to help support the smooth running of EOS. If you think our work is important we would love you to consider voting for our BP Team “eosmetaliobp”
Please be free to contact us if you have suggestions or questions
