If improving the stability of the beacon chain is not a good enough reason for you to switch from Prysm to either Teku or Nimbus, you also need to consider that due to the design of the beacon chain you will be subject to severe financial penalties if Prysm ever has an issue. ~Lamboshi on Twitter
graffiti, a custom message included in blocks your validator successfully proposes.
MY_GRAFFITIvariable. Feel free to customize your graffiti message between the single quotes.
<my infura Project's ENDPOINT>with your Infura endpoint and then run the following command to set the
To Action From-- ------ ----[ 1] 22/tcp ALLOW IN Anywhere # SSH[ 2] 9000/tcp ALLOW IN Anywhere # eth2 p2p traffic[ 3] 9000/udp ALLOW IN Anywhere # eth2 p2p traffic[ 4] 30303/tcp ALLOW IN Anywhere # eth1[ 5] 22/tcp (v6) ALLOW IN Anywhere (v6) # SSH[ 6] 9000/tcp (v6) ALLOW IN Anywhere (v6) # eth2 p2p traffic[ 7] 9000/udp (v6) ALLOW IN Anywhere (v6) # eth2 p2p traffic[ 8] 30303/tcp (v6) ALLOW IN Anywhere (v6) # eth1
validator_keysdirectory to the data directory we created above and remove the extra deposit_data file. If you no longer have the validator keys on your node, you will need to restore from file backup or restore from secret recovery phrase.
my_keystore_password_goes_herewith your keystore password between the single quotation marks and then run the command to save it to validators-password.txt
prometheus.ymlconfiguration file to match Teku's metric's settings.