Satoshi Qazi Muhammed
405fb9ce30
Connected to Asset Hub, the staking page asked the relay for derive.staking.validators. The api only offers the staking derives on a chain with the staking pallet, and the Pezkuwi relay carries only stakingAhClient, so rcApi.derive.staking is undefined: the page rendered, then crashed with "reading 'validators'" once the relay api connected. Neither chain can answer that derive alone. Take the active set from the relay's session.validators (Asset Hub's session set is its collators) and the next elected set from Asset Hub, where staking lives, in the shape the derive returns.
@pezkuwi/app-staking-async
With Asset Hub migration, the workflow of the staking system will change. The "user interactions" (nominate, bond, etc) are by and large the same, yet some details outlined below will change:
On the relay chain, the session pallet will rotate session (aka. epochs) at a fixed rate as it did before. It will send these to AH in the form of a SessionReport message. Possibly, it will also send messages about offences to AH so that they can be applied and actually slash staker balances in AH.
pallet-session on the relay chain will only interact with pallet-staking-async-ah-client. ah-client could at any point, if it has one, return a validator set to session to be used for the next session.
In any session change in pallet-session where a new validator set is activated, that SessionReport will contain two pieces of information:
More Info can be found here - https://hackmd.io/7PiBrGxxRG2ib-WRZYJZhQ