-
Notifications
You must be signed in to change notification settings - Fork 52
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
Implement Auto Top Up Worker #395
Comments
Need #398 |
Started compiling a design chart |
just for transparency, after a discussion we agreed there is a way to implement it without dependency on auth |
Also extracts common CLI command preps and tear downs to a function refs #395
Right now there's a limitation of Implement 2 new master wallets specifically for Auto Top Up. 1 wallet should serve for uakt top ups, and another for usdc grants. |
Also extracts common CLI command preps and tear downs to a function refs #395
So that those could be used separately for managed wallets, uakt and usdc top up refs #395
So that those could be used separately for managed wallets, uakt and usdc top up refs #395
… top up Also assembles rough service interface for further development refs #395
… top up Also assembles rough service interface for further development refs #395
also adds error handling for individual owner processing refs #395
…op up As a part of this: - implements allowance http service pagination limit - also adds error handling for individual owner processing refs #395
…op up As a part of this: - implements allowance http service pagination limit - also adds error handling for individual owner processing refs #395
…op up As a part of this: - implements allowance http service pagination limit - also adds error handling for individual owner processing refs #395
to ease testing in deployed env refs #395
Also rework managed top up logic to rely on user wallets instead of grants refs #395
to ease testing in deployed env refs #395
to ease testing in deployed env refs #395
to ease testing in deployed env refs #395
Also rework managed top up logic to rely on user wallets instead of grants refs #395
to ease testing in deployed env refs #395
Also rework managed top up logic to rely on user wallets instead of grants refs #395
to ease testing in deployed env refs #395
Objective
Implement a worker CLI handler that automatically adds funds (top-ups) to Akash Network deployments when they are low on balance. This ensures deployments continue to run without requiring users to manually monitor and replenish funds, improving the user experience.
Scope
Details
General Workflow
Target Owners Detection
Draining Deployments Detection (per every owner)
Top-up Action (per every deployment)
Acceptance Criteria
Calculations
The above can be used to calculate the time when a deployment is expected to close. To achieve that average block time is needed which can be found in
apps/api
constants.ts
orblocksService.ts
.Important to include job run interval into calculations to ensure not missing the time of closure.
To calculate amount to top up we need to get a number of blocks per time unit which is duration / average block time and multiply that by blockRate.
Design Chart For Reference
Link
Initial task version below
The text was updated successfully, but these errors were encountered: