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
See whitepaper: 5.5 Reinsert pot:
... when validators are inactive for 10 years...
we need to set the validatorLastSuccess mapping to the current timestamp when the validator became available.
it is currently not used, and we can rename this variable to validatorAvailableSinceLastWrite, or suggest a better name.
it should resemble when the last "available since" was written, but never turns 0 again.
to figure out if a validator was available or not since 10 years we have to check if 10 years have passed since the last write of availability, or if the validator was available since 10 years.
Implement as public available function that move all coins (those from validator candidates and those that have delegated coins on it.
See whitepaper: 5.5 Reinsert pot:
... when validators are inactive for 10 years...
we need to set the
validatorLastSuccess
mapping to the current timestamp when the validator became available.it is currently not used, and we can rename this variable to
validatorAvailableSinceLastWrite
, or suggest a better name.it should resemble when the last "available since" was written, but never turns 0 again.
to figure out if a validator was available or not since 10 years we have to check if 10 years have passed since the last write of availability, or if the validator was available since 10 years.
Implement as public available function that move all coins (those from validator candidates and those that have delegated coins on it.
https://bit.diamonds/wp-content/uploads/DMD_wp.pdf
because of time manipulation within the contracts: #175
The text was updated successfully, but these errors were encountered: