-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solana on Akash #193
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 1000.0 OTHER attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 2 weeks, 3 days from now. 1) amrosaeed has started work. The problem is the absence of a meta package of Solana SDK based docker images that allows Solana Devs to Have a (dedicated) Solana RPC clusters running on Akash network that’s local to developer’s app . By running Deidicated Solana RPC cluster on Akash it will allow Devs at 1/3 of the costs relative to AWS, to autoscale based on user demand, relax rate limits according to their application, and have peace of mind that other applications’ users won’t crowd their’s out. Learn more on the Gitcoin Issue Details page. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 1000.0 OTHER has been submitted by:
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 1000.0 OTHER attached to this issue has been approved & issued to @amrosaeed.
|
We are offering a 1000 AKT bounty to build a scalable Solana RPC cluster on Akash.
Having dedicated Solana RPC clusters that’s local to your app improves the performs significantly better than using a shared one. Akash is a decentralized open source cloud that offers low compute at one-third the cost of AWS, perfect for cost-efficient workloads.
Requirements:
Extra Points:
Solana References
Akash Resources
Registration Process:
Submission Process
Write a post detailing your work on the Akash forum. This post should include:
The text was updated successfully, but these errors were encountered: