Akash archival node HTTPS/WSS public API #263
aqt01
started this conversation in
Governance Proposals
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Abstract
Nodefleet is a Web3 blockchain and node running company focused on delivering value for investors/builders on the Pocket Network ecosystem providing top quality engineering and quality infrastructure around all of its products.
We are among the top providers on pocket.network with all of our pocket network domains combined we process around 117-150m requests per day served with around 23 different blockchains nodes across 3 regions; Southeast Asia, North America and Central Europe. The last 30 days we've had a total of 3.6 billion requests processed (attached in the links section).
With our experience on infrastructure development and open source space, we would love to collaborate by providing reliable connection to AKASH archival nodes through HTTPS/WSS endpoints on the US-EAST region.
By delivering this Akash archival node infrastructure, we also are going to empower the community and the akash team with access to historical data, the opportunity to index relevant on-chain akash information through the nodes, a healthy high threshold limit for Request Per Seconds to avoid DDoS attacks among other security measures and a high threshold of API monthly calls for heavy usage.
References:
https://nodefleet.org/
https://twitter.com/nodefleet/
Domains controlled by nodefleet:
https://www.poktscan.com/node_runner?domain=nodefleet.org
https://www.poktscan.com/node_runner?domain=blackholestake.io
https://www.poktscan.com/node_runner?domain=whiteholestake.io
https://www.poktscan.com/node_runner?domain=lightspeedstake.io
Proposed Solutions
HTTPS/WSS access will be provided to 2 Akash archival nodes deployed on high quality bare metal machines in order to provide stable quality, resilience, low latency and high availability infrastructure access for the Akash team and community. The nodes will be deployed in US-EAST and/or any region requested by the Akash governance team.
Additionally, we are going to implement infrastructure and network traffic metrics on a grafana real time dashboard for monitoring the health and usage of the infrastructure with relevant alarms via custom channel for having a transparent communication and status about our systems. Also we are going to include engineering/maintenance support for software updates and interventions requested by the akash team in case it is needed.
In case the foundation wants to take a more conservative cost saving alternative, we can just deploy one akash archival node which will represent a 50% reduction of the total cost monthly but with the downside of sacrificing availbility / service capacity.
Funding Request & Timeline
In order to implement a solid infrastructure access via HTTPS/WS for akash archival nodes we request 8k USD monthly upfront for the hardware cost and maintenance, engineer support for 2 Akash archival nodes in US-EAST region.
Implementation timeline (3 weeks)
Maintenance
Maintenance includes the following details:
Deliverables:
Below are listed the deliverables items after the development phase is completed:
Conclusion
We understand that providing a solid Akash archival node it’s important to serve as support for the current core systems, analytics platforms, research purposes among other purposes. By funding this proposal our team will be able to address the lack of availability of access to Akash archival nodes on the network.
Beta Was this translation helpful? Give feedback.
All reactions