You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Demote the HRMP channel management upward message kinds to regular entrypoints.
First reaction is that these entrypoints should go into the Router module.
I think it might also imply changing ValidationData structs. The reason is the following. Currently if the collator provides invalid data to the PVF and then PVF does something nonsensical then the candidate is rejected and collator misses out. With dispatchables the candidate becomes valid and we need to pass the required data through the ground truth (if any) to inform the PVF. On the other hand, we may want to remove some stuff from the TransientValidationData.
Demote the HRMP channel management upward message kinds to regular entrypoints.
First reaction is that these entrypoints should go into the
Router
module.I think it might also imply changing
ValidationData
structs. The reason is the following. Currently if the collator provides invalid data to the PVF and then PVF does something nonsensical then the candidate is rejected and collator misses out. With dispatchables the candidate becomes valid and we need to pass the required data through the ground truth (if any) to inform the PVF. On the other hand, we may want to remove some stuff from theTransientValidationData
.Related #1702
The text was updated successfully, but these errors were encountered: