From ab8d1b612c0dfbbccabb4b600f247369271e23aa Mon Sep 17 00:00:00 2001 From: Robert Habermeier Date: Mon, 31 Jul 2023 09:29:56 -0500 Subject: [PATCH] add necessary braces --- text/0003-blockspace-regions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0003-blockspace-regions.md b/text/0003-blockspace-regions.md index f304b48..35457f2 100644 --- a/text/0003-blockspace-regions.md +++ b/text/0003-blockspace-regions.md @@ -153,7 +153,7 @@ Created regions for a core MUST NOT exceed a combined block rate of 1 at any blo Regions are used to modify the behavior of the parachain backing/availability pipeline. The first major change is that parachain candidates submitted to the relay-chain in the `ParasInherent` will be annotated with the `RegionId` that they are intended to occupy. Validators and collators do the work of figuring out which blocks are assigned to which regions, lifting the burden of granular scheduling off of the relay chain. The **maximum consumption** of a region at any block number `now` is given by: -`maximum_consumption(now, region) = min(now, end) - start * rate` +`maximum_consumption(now, region) = (min(now, end) - start) * rate` If `end` is `None`, it is treated as infinite. The **minimum consumption** of a region at any block number `now` is given by: