EOSphere Guild — May`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 May 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.
It has been another productive month for our Guild. The Perth DC build out is coming along nicely with the true test happening this month when our WAX Hyperion Full History will go into production now served from Perth.
This last month we have also been participating on the Antelope Spring Beta-1 Testnet which is currently testing the Savanna Consensus Algorithm. Savanna brings near instant finality to transactions and I’m sure will make it’s way to WAX at some point as the code is adopted in the future. You can read more about it here.
v0.1 Beta of HeadsUp our Monitoring and Alerts Platform will be released imminently, final testing of the last RC is almost complete. Once publicly available we intended to update documentation, make usage videos and spread the news of it’s value across our socials.
On to the update:
Technical Operations
Infrastructure and services are currently operating normally and the network is well utilised as usual.
Our Store-1 server that hosts our public Hyperion Snapshots was extremely utilised this last month, I don’t think I have ever seen 1Gb/s of internet traffic for a single server on our infrastructure before.
We have continued rolling out upgrades to WAX v5.0.1 using the latest Antelope Leap code, mainly just organically. I expect us to be completely upgraded this next month.
Our WAX Mainnet Hyperion Service will be migrated to our Perth DC this month. The primary reason is the cost of Enterprise NVMe SSD’s, it’s more cost effective and easier to procure our own hardware in our own DC rather than lease from a bare metal provider. Interestingly we have provisioned the exact same Dell 740XD server in our Perth DC, so queries appear to be just as fast as before.
EOSphere WAX API Statistics (Last 2 weeks)
Global usage distribution is far and wide with the most concentrated usage being from the US, Germany, Thailand, Indonesia, Malaysia, Singapore and the Philippines.
55.69% of requests are WAX Hyperion Full History requests, 44.31% are normal WAX Software requests. In total over 348 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 12–22 Million successful “200” HTTP requests per day. This is about the same as last month where we were serving between 14–18 Million.
Interesting is appears that their was a specific IP address trigging our “API Abuse” policy resulting in a 429 “Too Many Requests” HTTP response.
This IP was querying our API more than 1000 times / 5 seconds for days at a time.
This lists the top 25 request types over the last 2 weeks, it’s quite clear that “get_table_rows” for HTTP v2.0 (37 Million Requests) and HTTP v1.1 (50 Million Requests) are still requested most by our users.
Results are a bit skewed this last period due to the “Too Many Requests” 429 policy being triggered. Over 193 Million requests hit this policy this last two weeks.
Not all queries have referrals, but of those that did most referrals came from Lazybones 25.33%, Alienworlds 13.31%, WAX Cloud Wallet 7.44% and Green Rabbit Game 5.6%
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
In this last period, the HeadsUp Team have been testing the release candidate that will be used as final for the v0.1 Beta as all phase features have now been incorporated.
As you have heard us mention before we have found bugs and tricky gremlins that needed to be taken care of.
However we are in the home straight, with only one issue remaining.
We expect to release v0.1 in the coming week.
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 added another guide to our WAX Hyperion Full History Series, that details setting up Data Tiering in your Elasticsearch cluster to make more effective use of your hardware resources.
Using Data Tiers with WAX Hyperion Full History
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
