New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reactivate Hancock Kusama Validator on `n4` cloud VM #12

Open

7 tasks

mgravitt opened this issue Mar 4, 2022 · 0 comments

Open

7 tasks

Reactivate Hancock Kusama Validator on `n4` cloud VM #12

mgravitt opened this issue Mar 4, 2022 · 0 comments

Contributor

mgravitt commented Mar 4, 2022 •

edited by amatsonkali

Prerequisites

Set-up monitoring tools for the kusama node (see Set-up Prometheus/Graphana for the Kusama node #22 )
Expand n4 storage (currently at 633G/776G, ~82% of usage)
Enforce some best practices for n4
Optional: In case that a new polkadot version is released, update the node.
Optional: Stablish a plan to avoid node downtime (Note: a high-availability set-up is prone to errors and hard to manage, requires advanced knoledge)

Steps

Have a separate stash and controller account.
Have a minimum bonded stash in their accounts (50 KSM)
Have a verified on-chain identity.
Connect to a private telemetry.
Determine the commision rate (Charge no more than 10% commission).
Apply to the programme by filling the form
- Optional: In case that the bonded KSM is less than 10 KSM, fill the "Case for good intentions" form.

Useful info

Secure a node
How to upgrade a node
How to monitor a node
How to chill a node

amatsonkali self-assigned this

amatsonkali removed their assignment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment