and welcome to our community forum! Let me help you with these questions
- depends on what you are planning to update or upgrade, as well how big (in terms of stake and pledge) your pool is.
Small pool, when quick fix is needed:
if the downtime is needed to update a new version or updating certificates, then i would just restart the node as 1.19. starts rather quickly (~15 sec), so the chances to miss a block are rather slim.
The only thing you should do to avoid long startup is to shutdown the node gracefully:
- from LiveView / TUI ( Text-based User Interface) hitting the Q button and waiting till process exits
- if you are running in SimpeView:
killall -SIGINT cardano-node
- if you are running using systemd
sudo service cardano-node restart
Extensive / time consuming repairs/downtime:
basically you boot up a copy of your BP node and do all the necessary upgrades, when it’s done, then point your relays to this server (by replacing the IP addresses in the topology file). That’ s it.
If you are using cloud VPS like AWS/GCP, then it’s easier, as you can boot a copy of your node and just re-asign the IP to the new VM and you don’t need to change anything in Relays.
2. Keys you need on your BP node
you need only these 3 files on that server, never EVER put any other key on the server (even temporary)
KES Singing Key (hot KES Key) - usually named hot.skey
VRF Signing Key - usually named vrf.skey
Node Operation Certificate - usually named op.cert
3. Yes, that’ s the advantage of POS approach. You just need your 3 files and compiled cardano node on a server to run a pool. All you need is:
- get/compile the carano-node / cardano-cli binaries on that new server
- copy all the keys/certificates
- point your relay nodes to this server
Let me know if you need any more assistance,