You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that withdrawals are enabled, I would like to generate pre-signed voluntary exit messages as insurance against a nuclear meltdown on my staking box, i.e. something that would cause a long offline period (e.g. natural disaster, hardware failure, etc). This could generate a JSON file with the signed data, which could be backed up on another device and later broadcast to any available beacon node (e.g. there are public nodes which could be used to broadcast without an active staking box). Obviously this would be for emergencies only, as I would be signing up for ~4 days of penalties prior to exiting, but it would bound the risk of running a staker.
Currently, voluntary exits on Lighthouse assume you are exiting immediately - it would be much appreciated if you could add a flag to decouple this from the actual signing process (e.g. --prepare-offline).
The text was updated successfully, but these errors were encountered:
Now that withdrawals are enabled, I would like to generate pre-signed voluntary exit messages as insurance against a nuclear meltdown on my staking box, i.e. something that would cause a long offline period (e.g. natural disaster, hardware failure, etc). This could generate a JSON file with the signed data, which could be backed up on another device and later broadcast to any available beacon node (e.g. there are public nodes which could be used to broadcast without an active staking box). Obviously this would be for emergencies only, as I would be signing up for ~4 days of penalties prior to exiting, but it would bound the risk of running a staker.
Currently, voluntary exits on Lighthouse assume you are exiting immediately - it would be much appreciated if you could add a flag to decouple this from the actual signing process (e.g.
--prepare-offline
).The text was updated successfully, but these errors were encountered: