Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

async backing: fetch prospective parachains config from the Runtime #6163

Closed
slumber opened this issue Oct 18, 2022 · 1 comment
Closed

async backing: fetch prospective parachains config from the Runtime #6163

slumber opened this issue Oct 18, 2022 · 1 comment
Labels
E0-runtime_migration PR introduces code that might require downstream chains to run a runtime upgrade.

Comments

@slumber
Copy link
Contributor

slumber commented Oct 18, 2022

// The maximum depth the subsystem will allow. 'depth' is defined as the
// amount of blocks between the para head in a relay-chain block's state
// and a candidate with a particular relay-parent.
//
// This value is chosen mostly for reasons of resource-limitation.
// Without it, a malicious validator group could create arbitrarily long,
// useless prospective parachains and DoS honest nodes.
const MAX_DEPTH: usize = 4;
// The maximum ancestry we support.
const MAX_ANCESTRY: usize = 5;

These values should be in sync with the Runtime.

Related #4841

@slumber slumber added the E0-runtime_migration PR introduces code that might require downstream chains to run a runtime upgrade. label Oct 18, 2022
@rphmeier
Copy link
Contributor

rphmeier commented Oct 18, 2022

I think the biggest question is whether we want these things to vary on a per-block basis (or even per-chain) or per-session. The easiest thing for the moment would be per-session: bake it into the HostConfiguration and have the same values for every chain.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E0-runtime_migration PR introduces code that might require downstream chains to run a runtime upgrade.
Projects
None yet
Development

No branches or pull requests

2 participants