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
Now that async backing has been successfully enabled on all networks, we could remove a lot of code that dealt with async backing not being present (the AsyncBackingParams runtime API not being present). The runtime API is actually the trigger for the node subsystems (not the actual values of the params).
If sync backing is desired, one may still use zeroed AsyncBackingParams.
Some subsystems which explicitly dealt with this: collator-protocol, backing, provisioner.
I believe we may also remove the legacy statement-distribution subsystem
The text was updated successfully, but these errors were encountered:
Now that async backing has been successfully enabled on all networks, we could remove a lot of code that dealt with async backing not being present (the
AsyncBackingParams
runtime API not being present). The runtime API is actually the trigger for the node subsystems (not the actual values of the params).If sync backing is desired, one may still use zeroed
AsyncBackingParams
.Some subsystems which explicitly dealt with this: collator-protocol, backing, provisioner.
I believe we may also remove the legacy statement-distribution subsystem
The text was updated successfully, but these errors were encountered: