List view
Akash users would like to be notified when a provider intends to go offline for maintenance or has an outage.
Due by October 30, 2025•0/4 issues closedAEP-74
Overdue by 11 day(s)•Due by October 15, 2025•0/3 issues closedWith Usage, Billing, API Keys and more getting added to Settings, it's time to rethink UI
Overdue by 26 day(s)•Due by September 30, 2025•0/1 issues closedAEP-73
Due by November 30, 2025Feature to let Console Users/ Customers forward container logs to logging services like datadog
Due by October 31, 2025•5/5 issues closedhttps://akash.network/roadmap/aep-70/
Due by October 31, 2025•1/5 issues closed## Why The API architecture and routing is currently split into 2 different approaches. The older approach was to have the routes under the [routers](https://github.com/akash-network/console/tree/main/apps/api/src/routers) and [router](https://github.com/akash-network/console/tree/main/apps/api/src/routes). The version of the endpoints is defined by the [v1](https://github.com/akash-network/console/tree/main/apps/api/src/routes/v1) folder name and all the routes are defined under the current version folder and organized by different "module" We then have a separate [api router](https://github.com/akash-network/console/blob/main/apps/api/src/routers/apiRouter.ts) and [other routers](https://github.com/akash-network/console/blob/main/apps/api/src/app.ts#L74-L101) defined in the root app. The newer approach which defined modules at the root and under each [module](https://github.com/akash-network/console/tree/main/apps/api/src/billing) the routes of that specific module, which properly separates the concern of each business logic. We want to refactor the routes to have them under the same unified swagger definition and unified routes/router implementation with modules. ## What - Refactor the old routes under properly defined modules with route -> controller -> service -> repository architecture - Rename the files of the router definition in the router file and service file, for example: ``` start-trial.v1.router.ts start-trial.v2.router.ts ``` - Refactor the swagger definition to have the routes all under the same swagger route
Due by November 28, 2025•3/5 issues closedSteps to improve onboarding experience for legit users
Overdue by 1 month(s)•Due by September 26, 2025•11/13 issues closedValidating whether an SDL will result in any bids or not *before* a transaction is created
Overdue by 26 day(s)•Due by September 30, 2025•1/3 issues closedImplement the new typescript chain sdk client library which exposes protobuf types, grpc client/gateway and merge the code from akashjs. https://github.com/akash-network/akashjs/milestone/4
Overdue by 2 day(s)•Due by October 24, 2025•0/2 issues closedAutomated Console API and UI tests that are run as part of the CI pipeline
Due by December 31, 2025•5/11 issues closed### Project Convergence **Description** We want to unify our codebase’s developer experience by standardizing architecture, dependencies, naming conventions, and CI/CD pipelines across all our projects and packages. This will reduce onboarding friction, enable easier cross-project contributions, and create a more welcoming environment for our community. **Goals** 1. **Design & Document** - Produce clear guidelines for desired architecture, tooling, naming conventions, and directory structures. 2. **Migration Plan** - Outline a phased approach to refactoring and updating codebases with minimal disruption, using “lazy” migration strategies as new features are developed. 3. **Community Involvement** - Provide clear instructions for refactoring tasks so that contributions can be delegated to the community in a controlled manner. 4. **Ongoing Refactoring** - Gradually unify existing projects and packages under common standards, ensuring consistent CI/CD and infrastructure as we go. **Outcome** By converging on consistent dev practices, we will streamline contributor onboarding, foster smoother collaboration, and maintain a healthier open-source community.
Due by December 31, 2025•0/2 issues closedWe rely on chain data heavily in the UIs. In the past to move faster the lists rendering records from chain were fetched without a pagination. Obviously it's got some performance implications. This is a milestone to implement proper list data fetching and rendering.
Due by December 31, 2025•1/5 issues closed- Overdue by 26 day(s)•Due by September 30, 2025•22/39 issues closed
- Due by December 31, 2025•6/8 issues closed
We have a [logger](https://github.com/akash-network/console/blob/main/apps/api/src/core/services/logger/logger.service.ts) in API which provides a proper interface and functionality for the purpose. We need to be able to use it in other packages/apps/project. For this it needs to be updated to work in both browser and backend and published to npm.
Due by December 31, 2025•7/9 issues closed