Automatic pool reassignments
Having a trigger (or something else) that keeps checking if a machine is hashing to the correct subaccount.
A few examples :
- A client isn't paying his bill and we have to move it to a different subaccount, tagging them with “Delinquent” and having that trigger check if it's on the different subaccount, if not, changes it.
- A machine should be hashing to a specific subaccount/worker (custom field “Expected worker”) and isn't for any reason, update the subaccount/worker to match the “Expected worker”.
Invalid pool config is something that could work in some cases, like self-mining where you have one subaccount for the whole fleet, but when you have multiple clients, it gets complicated.
Comments
1 comment
We assign valid pool settings at the sub account/client, and then do invalid pool check at the parent level based on client. That way, if client is changed from the parent level, the invalid pool is triggered and the correct pool for the new client is updated. But, yeah, in retail this has to cumbersome as all get out.
Please sign in to leave a comment.