Hyperion History Updates
All the improvements on Hyperion History since it first launched!
It has been six months since Hyperion History was launched and we are extremely happy to see the community adopting and evolving the project with us. This has always been the goal of EOS Rio when open-sourcing the project, hoping amazing talents in the community take it further than we could ever imagine.
Hyperion nodes are deployed on 7 EOSIO chains and 3 testnets, and operated by 4 teams in addition to EOS Rio. A huge shout out to eos sw/eden, EOS Nation, CryptoLions, EOS-USA and all the other teams contributing to evolving the solution. If you want more information or need help setting up/operating a node, just join our Telegram group at https://t.me/EOSHyperion. Some of the best engineers on the EOSIO ecosystem are already there.
This is just the beginning and we keep working hard to improve Hyperion History and make life easier for dApp developers. It is amazing how much more we were able to learn about EOSIO uses and the state of the community. This makes us even more confident about EOSIO future.
Here we list the evolution we had since launching and what’s ahead for Hyperion.
Robustness
One of the main focuses so far, this is often an invisible work but primordial to operate a mission-critical infrastructure. A collection of small changes makes Hyperion much more robust than just a few months ago, and it is still evolving.
One example is the Integrity check scripts that continually scans the database for missing blocks and repair them automatically. Crash recovery features make it easier to operate Hyperion, significantly reducing downtimes and replay times, making it even more reliable. And much more is on the works by the community of engineers currently contributing to Hyperion. EOS Rio is working on architectural adjustments, Hyperion environment monitoring, and documentation.
EOSIO V1.8 Compatibility
Hyperion History code is already compatible with EOSIO v1.8.
Flexibility
Once developers started using Hyperion, the team began receiving demands for new API calls to use cases we have not anticipated. We have been working on adding different types of calls and even creating a History API v1.0 interpreter allowing developers to use v1 calls on Hyperion. This is a non-stop work to support as many use cases as possible.
Scalability
Hyperion was able to change the rules on storage scalability, but it still relies on REST APIs, which has proven to be suboptimal, considering the characteristics of the database, application architecture, and queries. To increase vertical scalability, the development of Websocket APIs was included on the roadmap.
None of this would be possible without the community, especially those on the Hyperion Telegram group. Thank you all for making this happen.
If you want to support Hyperion even further
- vote eosriobrazil on EOS mainnet
- vote bosriobrazil on BOS mainnet
- Support Hyperion Proposal for BOS WPS (https://www.boswps.io/#/poll_detail?proposal=hyperion.api)
Useful Links
Documentation: https://eos.hyperion.eosrio.io/v2/docs/index.html
Source code: https://github.com/eosrio/Hyperion-History-API
Javascript Library: https://github.com/eoscafe/hyperion-api
Public Endpoints
EOS mainnet
▸ http://api.eossweden.org/v2/docs
▸ https://mainnet.eosn.io/v2/docs
BOS mainnet
▸ http://api.bossweden.org/v2/docs
▸ https://bos.eosusa.news/v2/docs (🚧under maintenance)
WAX mainnet
▸ https://api.waxsweden.org/v2/docs
▸ https://wax.eosusa.news/v2/docs
WORBLI mainnet
▸https://api.worblisweden.org/v2/docs
INSTAR mainnet
▸ https://instar.eosusa.news/v2/docs (🚧under maintenance)
MEET.ONE mainnet
▸https://api.meetsweden.org/v2/docs
TLOS mainnet
▸ https://mainnet.telosusa.io/v2/docs
Kylin Testnet
▸ https://kylin.eosusa.news/v2/docs
▸ https://kylin.eosn.io/v2/docs
▸ https://kylin.eossweden.org/v2/docs
Jungle Testnet
▸ https://junglehistory.cryptolions.io/v2/docs
▸ https://jungle.eosn.io/v2/docs
▸ https://jungle.eossweden.org/v2/docs
▸ https://jungle.eosusa.news/v2/docs
