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
When a staker that has 0 active balance sends a setActiveStake transaction that sets the active balance to 0, no balance is moved but the inactiveFrom block is still reset to the next election block, resetting the inactivation wait timer.
The text was updated successfully, but these errors were encountered:
Sounds like reasonable behavior to not special-case this. Does any problem result from this behavior? If the staker sends such a transaction despite not needing it, that's on themselves IMO.
When a staker that has 0 active balance sends a
setActiveStake
transaction that sets the active balance to 0, no balance is moved but theinactiveFrom
block is still reset to the next election block, resetting the inactivation wait timer.The text was updated successfully, but these errors were encountered: