Skip to content
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

Bid Storm Mitigation - Max bids pr hour - customizable provider feature. #263

Open
2 tasks done
SGC41 opened this issue Nov 8, 2024 · 1 comment
Open
2 tasks done
Assignees
Labels
repo/provider Akash provider-services repo issues

Comments

@SGC41
Copy link

SGC41 commented Nov 8, 2024

Is your feature request related to a problem? Please describe.

With the recent Trial super high activity and some recent testing by yours truly.

I enabled USDC again last night, wanted to see just how bad the crazy activity was....

Wanted to see if there was any real USDC work, because ATK network has been very quite...... like a few bids every few hours, or so.... very limited maybe 40-70 a day.

So i turned it on and was quickly a bit surprised about just how many bids i was seeing... also because my provider can't get leased, by the trial, due to the whitelist it will keep responding to every bid and thus giving me a clear view of exactly how busy it is.

i was going to check the last 12 or so do the math .... but i found myself nearly unable and atleast unwilling to do this due to the time, it would take with the tools i'm currently using... i'm sure there are much better ways, but i'm not a blockchain engineer.
so what i usually do is count my wallet pages in mintscan, because they have 10 transactions each and then maybe subtract my withdrawals, but since i got 3 lease and a 6 hour withdrawal rate that will be pretty irrelevant.

i counted 104 pages in the last 3 hours... that would make it 8160 bids in a 24 hour period.

hench 8160 x 0.004 = 32 AKT a day or 78$ a day
2340 $ a month in bidding fees....
🆘 📛

.... bid storms ... for a lack of a better definition.

if one has hardware that isn't being selected and the bids are not very hardware restrictive, many providers might still bid...

Describe the solution you'd like

i would suggest we need a sort of customizable bid delay / max per hour in our provider.yaml
so we could set a provider to not bid more than is reasonable for, what it can earn...

Describe alternatives you've considered

duno if this is the best solution for this.... i'm ofc open to better ideas.
but its what i got thus far

Search

  • I did search for other open and closed issues before opening this

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

No response

@chainzero chainzero added repo/provider Akash provider-services repo issues and removed awaiting-triage labels Nov 20, 2024
@chainzero chainzero self-assigned this Nov 20, 2024
@chainzero
Copy link
Collaborator

Immediate issue/concern and as it pertains to Trial bids has been addressed by provider signed attributes. I.e. the only providers on the network that will bid on trial workloads are those that are participating in Akash Trials. This spares community providers that are not part of the program from associated bid fees.

This leaves the remaining question - is there sufficient need or cause to protect providers from bid storms otherwise. There are other safeguards in place - such as provider pricing script adjustments to eliminate bidding on small workloads if desired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repo/provider Akash provider-services repo issues
Projects
None yet
Development

No branches or pull requests

2 participants