yeah, its a question how it becomes implemented.
I also think in general, every user should decide how to handle it.
I also think in general, every user should decide how to handle it.
getState shows "numberOfUsers":2
When user unlocks their account on the node, check against how many users are already forging on that node, check if AllowedForgingUsers is set to 'unlimited', allow to unlock, if the number is less than AllowedForgingUsers in web.xml - allow to unlock, and if it's equal to that parameter, display 'Node forging capacity is full' or something like that. Or do you see any other difficulties in implementing this? Please explain.
don't see any problem there.
Maybe it would make sense to replace unlimited by an defined number to avoid "Monopo(o)ls".
(don't know how to do in open source SW)
Big pools could become bigger and bigger due to more frequently forging.
This allure (more accounts => more frequently forging) + self gaining...
And in the end, we will have a big pool with all Nxts in it
