[Feature]: Automatic Redelegation to Backup Validator in Case of Validator Jailing

[PrathyushaLakkireddy]

Summary

When a validator is jailed, delegators may lose staking rewards due to a lack of awareness and the need for manual intervention to check and redelegate their stakes.

Problem Definition

Delegators may not always be aware when their validator is jailed, requiring them to manually check the situation and redelegate their stakes. This manual process can result in a loss of staking rewards.

Proposed Feature

We can introduce a backup validators system that would automatically redelegate the delegator’s stake to a pre-selected backup validator in the event if the primary validator is jailed.

Key Features:
Automatic Redelegation: If a validator is jailed, the system would automatically redelegate the stake to a pre-designated backup validator.
Optional Opt-In: Delegators can choose a backup validators during the initial delegation process, or set one at any time.
Continuous Rewards: This feature ensures that rewards are not lost due to validator jailing.

[julienrbrt]

Thanks for proposing this!

This sounds more something for a third-party service, instead of having that backed in the protocol.
What if your backup validator is as well jailed? Do you time a time limit? As a validator can unjail itself.
Does it work only for tombstoned validators (which would make more sense).

All of this adds extra complexities, for not too much reason.
A third party could just demand a delegate authz grant and do all that logic off chain.