These are all the projects that are currently in some state ranging from “ideation” to “release”. To understand the various states see the table at the bottom of this page.
General guidelines for updating this table
- Projects that are in some working state (ideation or beyond) should have a link to their specific sig or wg page (can even just be a github issue inside the repo for the sig) from the “Project Name”
- Projects that are in a working state should have a label specified here and linked to a filtered list of github issues for that label
- Projects that are in a working state should be assigned to a SIG or WG
- Projects that are not even in ideation (not in a working state) should have a name and a brief description
List of Projects
| Project Name | Label | Description | Community Group | State |
|---|---|---|---|---|
| GPU Support | gpu | Everything related to supporting, launching and growing GPUs on Akash | wg-gpu | released |
| Stable payments & Settlement | Ability for tenants to pay for deployments using other cryptocurrencies | sig-economics | implementation | |
| Economics 2.0 | econ-2.0 | Redesigning Akash Network’s economics model to have fine grained take rates to fund product development and sustainability of the chain | sig-economics | released |
| Akash Website Revamp | Implement new website with refreshed designs and more maintanable tech stack | wg-website | Implementation | |
| Certification Program | edu-cert-prgm | Define, build and finalize Akash Network Certification Program | sig-education | implementation |
| Event Planning 2023 | Define purpose, lineups, and attendees (and weight of OCL presence) for events that Akash Network would attend | sig-community | Implementation | |
| Akash Hackathon | Define purpose, structure, timelines and outcomes | sig-community | released | |
| Docs site migration | docs-site-migration | Migrating the documentation site from gitbooks to something automatable (Hugo?) | sig-documentation | implementation |
| On-Chain Analytics | Build data pipeline and analysis tool for onchain analytics | sig-analytics | implementation | |
| Provider Attributes | provider-attr | Defining an attribute schema for providers and getting providers to incorporate it | wg-provider-attributes | implementation |
| Authorized Spend Management | authz | Supporting Authorized Spend (AuthZ) in Akash Console | sig-clients | released |
| Content Moderation | content-mod | Tools and process for ensuring that providers have visibility into workloads running on them and controls to ensure they don’t violate their terms of service | sig-providers | implementation |
| Client Libraries | client-libs | Libraries for deploying on Akash programmatically using various programming languages | sig-clients | implementation |
| Provider Services Microservices Refactor | provider-svc-split | Splitting Akash Provider Services into microservices so that we’re able to release and maintain software better | sig-providers | implementation |
| Provider Analytics | Analytics for providers to understand their profitability and ROI | sig-analytics | spec-definition | |
| Omnibus Maintenance | omnibus-maint | Building new reference SDLs and packages for new chains that we want to support. Building automated testing for the supported omnibus chains | sig-community | ideation |
| Keeping up with Cosmos | cosmos-sync | Things we Akash needs to do to stay in sync with Cosmos (SDK changes etc) | sig-support | |
| Private Image Repository | Support for deploying images hosted in private container registries | |||
| CI/ CD Workflows | Things necessary to support CI/ CD style deployments on Akash | |||
| Provider Attribute Auditing | Tooling for auditing provider attributes (like memory, CPU, bandwidth, storage and others) through automated testing before a provider is “officially signed” | |||
| Provider Monitoring | Hooks for being able to pull infrastructure metrics into tools like Prometheus and Grafana for monitoring and logging | |||
| Provider Pricing & Profitability | Tools for providers to set pricing and calculate profitability before they decide to become an Akash provider | |||
| Cloud Parity Foundational Features | Cross Provider Deployments for High Availability (HA). Load balancers. State Management | |||
| Cloud Parity Reference Applications | Building reference applications that mirror the way apps are built in public clouds | |||
| StorJ Integration | Spec and implement what’s needed for users to use StorJ for persistent storage (like S3 or Akash persistent storage) | |||
| Log Retention for Tenants | Support retaining tenant deployment logs for longer durations to allow better debugging | |||
| JWT Authentication | Authentication using Java Web Tokens | |||
| Container Image Updater | Ability to have a new version of a container image be redeployed when the registry image is updated | |||
| Reference Provider Setup | Build & Operate a reference provider(s) for Akash Network in a colocation facility. |
Project States
A project may be in one of these states. Note that every project does NOT have to touch every one of these states and some projects may remain in a given state for a long time (like an idea that never gets any interest from the community to implement and remains in “ideation” for a long time).
| State | Description | Things needed |
|---|---|---|
| ideation | A rough idea for a project has been proposed | |
| spec-definition | Specification (typically a PRD or a ligher version of it in a github issue) is being worked on by a SIG or WIG and is in review | |
| spec-approved | The specification for the project has been approved and it has been allocated to specific SIG(s) | |
| design | Technical Design is being worked on (typically by SIG(s) ) | |
| implementation | Actual work to bring the thing to life is happening (code being written, event being organized, docs site being updated) | |
| beta | The project is in beta test phase (where/ when applicable) - typically for products/ features | |
| released | The product/ feature has been released to everyone (general availability) | |
| blocked | The project is blocked or stalled because of some reason (documented) | |
| abandoned | The project has been cancelled because no one is willing to shepherd it |