Running a validator expects a lot of manual work or scripting. And while there is documentation here and there about the onchain actions you need to proceed (i.e. bond, validate). The process of session keys setup requires dealing with the node itself to generate the keys and write them into the keystore locally. Moreover you have to call session.set_keys and restart the node.
I think we could simplify this process by adding some wizard to the node itself. I mean some CLI, which would generate the keys, tell the user (or provide a link) how to set them on chain and stop the node at the end (so the user started it again, which would cause the reboot we need).
It could be an additional command, like ./atleta-node set_keys or something. Or we could even simpify the whole process of becoming a validator by ./atleta-node validate. This way we wouldn't need to distribute scripts additionaly to the node binary itself.
Running a validator expects a lot of manual work or scripting. And while there is documentation here and there about the onchain actions you need to proceed (i.e.
bond,validate). The process of session keys setup requires dealing with the node itself to generate the keys and write them into the keystore locally. Moreover you have to callsession.set_keysand restart the node.I think we could simplify this process by adding some wizard to the node itself. I mean some CLI, which would generate the keys, tell the user (or provide a link) how to set them on chain and stop the node at the end (so the user started it again, which would cause the reboot we need).
It could be an additional command, like
./atleta-node set_keysor something. Or we could even simpify the whole process of becoming a validator by./atleta-node validate. This way we wouldn't need to distribute scripts additionaly to the node binary itself.