EOSphere Guild — October`24 Update
EOSphere operate a Guild on the WAX Protocol Network providing infrastructure, services and initiatives with a focus on ensuring the health of the network, as well as assisting in the growth and adoption of the WAX Ecosystem.
Welcome to our October 2024 EOSphere Guild Update. This is where we publicly inform our WAX community of EOSphere’s last six weeks challenges and achievements, rather than just sharing them with the WAX Office of Inspector General (OIG) and peer Guilds.
While the global crypto community is waiting for the market to run with the bulls, the EOSphere Guild team have continued at it providing solid services for the WAX ecosystem.
This last month we have updated our HeadsUp Platform to v0.1.6 with additional features and bug fixes and we have joined the RIO Blocks QRY Core Team. What is QRY I hear you ask .. well stay connected to our socials and hear all about it over the coming weeks.
The highlight of the WAX ecosystem this last period was surely #WAXGamesWeek, where loads of awesome WAX ecosystem games are being showcased.
On to the update:
Technical Operations
Infrastructure and Services are currently operating well with the normal utilisation on the network.
We had an upstream internet outage in Perth for 90mins on the 7th/8th October due to an environmental issue experienced by our provider. All services restored successfully after the issue was remediated.
We have also started the process of refreshing our servers in Sydney, currently waiting on hardware.
EOSphere WAX API Statistics (Last 2 weeks)
Global usage distribution is far and wide with the most concentrated usage being from the USA, UK, France, Germany, Russia, Thailand, Malaysia and the Philippines.
51.93% of requests are normal WAX Software requests , 48.07% WAX are Hyperion Full History requests. In total over 280 Million user API requests over 2 weeks, excluding our Atomic Assets API which isn’t represented.
This represents the number of HTTP response codes over the last two weeks per 12 hours. Currently we serve around 8–16 Million successful “200” HTTP requests per day. Which is a bit higher compared to last month where we were serving between 8–13 Million.
Interesting spike on the 8th October which was our “too many requests” policy being triggered. More than 120 Million requests over 24 hours.
This IP was querying our API more than 1000 times / 5 seconds for a whole day.
This lists the top 25 request types over the last 2 weeks, it’s quite clear that “get_account” for HTTP v2.0 (38 Million Requests) and HTTP v1.1 (32 Million Requests) are requested most by our users.
Not all queries have referrals, but of those that did most referrals came from My Cloud Wallet 22.42% , Alienworlds 17.61%, Lanren 13.99% and Green (8.43%)
Please let us know in the comments if there are any specific statistics you would like to see in the next update. Elastic Stack has lots of granularity.
If you are having difficulty or are just curious in using our services you can always check uptime and availability statistics via our WAX Public Facing Service Dashboard.
Product Development
The EOSphere Team have just released HeadsUp v1.6.0 which is actually a rollup release of v1.4.0 and v1.5.0.
This release includes a multitude of bug fixes and new features 🏆:
- Removed the old buggy metric History API Connects and replaced it with a metric for ‘Last Indexed Action’. This is excellent to track whether your indexer is indexing actions in the indexed block.
- Fixed spelling of Address in Add Node window
- Fixed deleting of a chain deletes associated alerts
- Fixed an error showing that alerts had been active for 54 years
- Can now change the type of a node after creating it, without needing to delete and recreate
- Latency shows as N/A when node not connected
- Reminders for node not connected fixed
- Fixed an error causing ‘create node’ button to be clicked twice before creating node on some browsers
- Fixed an error causing default monitoring and alerting settings not to be applied upon creation
- Updated the silencing module to work for connects and latency alerts which take a URL parameter
- Added node sort_order to each row on the chain page node tables
- When creating a new node, the default value for sort_order reflects the next number up from the others in the table
- Changed the vote rank alert to be ‘alert me when vote rank changes’, allowing users to disable vote rank notifications by turning this off
Please join our Telegram Group for the latest release information as well as github links and instructions.
Business Development
A reminder that EOSphere offer Commercial Solutions for WAX Services.
We are able to host or operate your own infrastructure for the following:
Hyperion Full History
Atomic API
WAX Protocol Network API
At this point, we unfortunately aren’t able to provide this service to other WAX Guilds. However, you are welcome to use our ElasticSearch Snapshot Repository API.
Please contact us at info@eosphere.io to discuss your needs so we can craft a suitable solution for you.
Ecosystem Development
WAX Technical How To
If you are technically curious or interested in running services on the WAX network, be sure to have a look at our WAX Technical How To series published monthly in the EOSphere Blog on Medium.
These guides are being added to the WAX Developer GitHub.
This month we created a guide that covers how to configure and start receiving HeadsUp Alerts through Telegram using the Bot API.
Configure HeadsUp Telegram Alerts
Be sure to ask any questions in the EOSphere Telegram
EOSphere Guild is a Block Producer on the WAX Protocol Network as well as many other Antelope based Blockchains.
If you find our work helpful, please vote for us on the WAX Mainnet: eosphereiobp
If you prefer to proxy your vote, our proxy account is : blklotusprxy
Connect with EOSphere via these channels:
TELEGRAM | MEDIUM |YOUTUBE | FACEBOOK | TWITTER | INSTAGRAM
