Implementation of ah-client and rc-client staking pallets #7582
Conversation
tdimitrov
added
T2-pallets
| #[pallet::storage] | ||
| pub type ValidatorSet<T: Config> = StorageValue< | ||
| _, | ||
| Option<Vec<(T::AccountId, Exposure<T::AccountId, BalanceOf<T>>)>>, |
There was a problem hiding this comment.
A comment from @kianenigma
Also exposures will not be stored anywhere in RC anymore, so they should not be in this storage?
RC will only know the list of validators.
@Ank4n rasied the same point. He removed Exposure in his PR but since we are working in parallel I can't use its work here.
I'm leaving this as is for now and will remove it in the next PRs.
| } | ||
| } | ||
|
|
||
| fn start_session(session_index: u32) { |
There was a problem hiding this comment.
From @Ank4n (old comment)
What we do need to send is the block timestamp (unless @kianenigma thought of a better approach) when this pallet provides a new validator set to the session—essentially the timestamp marking an era change. This will help AH calculate staking rewards for validators in that era.
|
|
||
| /// Keeps track of the session points for each block author in the current session. | ||
| #[pallet::storage] | ||
| pub type BlockAuthors<T: Config> = StorageMap<_, Twox64Concat, AccountId32, u32, ValueQuery>; |
There was a problem hiding this comment.
TODO:
Also, I just realized that other than block authorship, the parachains protocol also adds points for parachain work.
…-staking` which is published
tdimitrov
changed the title
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
Recreation of #7357 on top of master. The old PR messes up the git history too much so I am recreating it from scratch.
This PR is work in progress. It's purpose is to commit initial structure of
pallet-staking-ah-clientandpallet-staking-rc-clientto master. The changes will be polished by a follow up PRs which will be backported.Related issues: #6167 and #6166
This PR introduces the initial structure for
pallet-ah-clientandpallet-rc-client. These pallets will reside on the relay chain and AssetHub, respectively, and will manage the interaction betweenpallet-sessionon the relay chain andpallet-stakingon AssetHub.Both pallets are experimental and not intended for production use.
TODOs: