You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main problem is current tokenomics. If a workload is deployed on my farm, I do not directly receive additional rewards for that. Yet I will incur a cost, as the energy consumption of my nodes rises. As such, farmers are incentivized to prevent workloads from being spawned on their nodes. If a farmer can mark his own nodes as dedicated, he will do so. Dedicated nodes must be rented in their entirety (and paid for in their entirety by the user), thus it becomes prohibitively expensive for users to deploy on these nodes (especially on large nodes), unless the user would have a use for the entirety of the node, which is rare. In other words, if the farmer can do this himself, most farmers would, which would drastically restrict the amount of nodes one can deploy on, thus having a severe impact on the utility of the grid. As a middle ground, the decision was made to allow for the council to do this, if a farmer has valid arguments and it would not impact the grid too much.
As a middle ground, the decision was made to allow for the council to do this, if a farmer has valid arguments and it would not impact the grid too much.
Thanks for your feedback, this is what I was suspecting.
I see the tokenomics point and why we should not incentivate dedicated farms creation.
Meanwhile a farmer can now set its farm as dedicated by setting an extra fee on it (see extra fee design here).
So the task is doable even if not facilitated (need to do it one by one).
As a farmer i want to be able to set my farm as dedicated without the effort of getting council approval
The text was updated successfully, but these errors were encountered: