Staking failsafes (80a51bf1) · Commits · Radu Popa / substrate

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Commit 80a51bf1 authored Aug 22, 2018 by

Gav

Browse files

Staking failsafes

- Don't slash/unstake/change session when too few staking participants
- Introduce set_balance PrivCall

parent 5919a6f0

Hide whitespace changes

Inline Side-by-side

Please register or to comment

Admin message

Staking failsafes