robert
robert
The GF(2^16) implementation @drskalman and I did is working, although unoptimized. We are using it for a fault-tolerant data replication service as part of a larger project.
I also approve. Ultimately, I think this is really going to come down to @tomaka's decision, since he's done most of the work on this project.
This is a good idea. I think we should at least create a place for it and then ask parachain teams to keep it updated
`AdvertiseCollation` in network v2 should have `(RelayParentHash, CandidateHash, ParentHeadDataHash)` where the relay-parent is the relay-parent of the candidate. The new `CollationFetchingRequest` needs to include the candidate hash. We'd use `GetMinimumRelayParent`...
Yeah. I opened a follow-up for the optimiation of the fetching rule as well
related: #5923
Yeah, @bredamatt please open a PR against the feature branch and file a follow-up issue to remove the test once synchronous backing is obsolete.
We should just merge `rh-async-backing-feature` with master. I believe @slumber has plans to do this in the near future
This should be pretty easy. The main issue AFAIK is that we are using `ctx` when polling each future currently and then processing reputation changes. But we should just change...