robert
robert
### Tracking - [x] Backwards compatible runtime changes: accept older relay-parents (#4786) - [ ] Deploy to Kusama - [ ] Deploy to Polkadot - [x] Implementation of 'Context' logic...
Closes #3779 Includes all asynchronous backing work. #4786 #4790 #4913 #5557 #5711 #5999 and more
If the runtime API version indicates that asynchronous backing is enabled, we'll need new logic in statement-distribution. ## Goals The statement-distribution subsystem has these high-level goals: 1. Distribute locally-generated statements...
A common issue is that parachains need to include data which is large and takes up PoV space. We can use the [Preimage pallet](https://github.com/paritytech/substrate/blob/master/frame/preimage/src/lib.rs) to have validators load this data...
#2947 introduces `disputes::RewardValidators` and `disputes::PunishValidators` traits which should be implemented for some type which can forward along the offences to the `pallet_offences` in such a way that they lead to...
Follows on to #5557 (currently based upon it, but I will rebase on the feature branch once that's merged) Closes #5055 . More details about the intended changeset can be...
https://github.com/paritytech/polkadot/pull/3348#discussion_r664462683 @eskimor Has been pushing strongly to include `ValidatorIndex` in the dispute statement. Our major disagreement has been over the fact that the `SignedDisputeStatement` can't actually check whether the public...
The network bridge was initially designed and implemented in late 2020, before we'd fully implemented all of the necessary networking protocols for parachains. At that time, we weren't sure whether...
It shouldn't require nearly as many allocations as it currently does in order to get the param types and tokens.
Vague description in https://github.com/darrenldl/reed-solomon-erasure/pull/34#issuecomment-451457992