Closed miloskriz closed 7 months ago
Thanks @miloskriz !
Paseo invulnerables have been now updated. You can see your new stash being part of the list
[
5FRmC9wUZjr2VRh1q5z1Beksh62nfPzpLuhyCkHRKWXjWv9u
5F2A2bL6WopW8NEmxQmABY8cLtYmdDjNzsiwnCDLtPn44orx
5Ea38N1YzxnfDEkGRNixPE4oXALAuMK4XDoYpH4fyZahdrLL
5Fgato4wJxwZicavjaKQ9oG5e2M1S5wUfy7mMxsw1HTw95ub
5CQN2L4soC8G6L3nngT42oTEc28BCmNvDEt5RwtpYV7QBScp
5EResBHk8rwXfd1fxrhUqR5b8fFHxkzCtLLk9GSopgAnmP5v
5GnMSvfjUpRSwyQyzbrFfGqAS6vhBnLGtQCmPDikshemP4Jh
5DDVAkXRMSkkmrB2yqrbFvPCZt8xaPawcy2bEvBsCJRRiUtm
5FJ7mri5qMgoAA1u6GptebqbPT1QXpPggoABrpgs2NJprKwz
5FRWXfgHjZVXs7BSP4yBB2b8fgczRof5zynJjbgud6ptRrUA
5DvoL2BNoSm7wRt2tfZ6WW5QFrxm68GLv5SCrPQ4JBLjbvpL
]
Question Overview
After onboarding 3x validators (1x invulnerable from genesis, 2x more by application in this PR) we would like to kindly request the invulnerability is changed to one of the new validators and after that we would like to chill and request to off-board the one from genesis (to be used as backup from then on).
Detailed Description
5CkHkUKgay1bA77oFWBkaw83fjdX1yQaaBHtWAghTmzxAv1U
5Fgato4wJxwZicavjaKQ9oG5e2M1S5wUfy7mMxsw1HTw95ub
We can confirm the new invulnerable is up an running, that the associated machine has very good performance (bare metal AMD Ryzen latest gen) and has strong resiliency (co-located in a tier III datacenter in Glasgow, Scotland) so fully compatible with the invulnerability responsibilities.
What You Have Tried
Foreseeing this change, we have requested the retroactive payouts for Q1 here for the 3x previous validators but adjusted the proactive payouts for Q2 here to keep only the 2x validators added to the formal submission.
Once the change of the invulnerability is done, we will chill the old validator stash, unbond the stake and make the funds available to be sent back to treasury upon request.
Expected Outcome
the result of the chain storage function staking.invulnerables() must return
5Fgato4wJxwZicavjaKQ9oG5e2M1S5wUfy7mMxsw1HTw95ub
instead of5CkHkUKgay1bA77oFWBkaw83fjdX1yQaaBHtWAghTmzxAv1U
.Environment
Additional Context
not applicable.