From 1cb5f0d91b8021b7c2b8c3ed8a3f687f453cd833 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Mon, 16 Oct 2023 19:23:18 +0100 Subject: [PATCH] Update text/0031-corejam.md Co-authored-by: Sergej Sakac <73715684+Szegoo@users.noreply.github.com> --- text/0031-corejam.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0031-corejam.md b/text/0031-corejam.md index 5e97172..bfc9a0f 100644 --- a/text/0031-corejam.md +++ b/text/0031-corejam.md @@ -337,7 +337,7 @@ While it will generally be the case that RcVGs know precisely which Work Reports #### Availability -Once the Work Report of a Work Package is Registered on-chain, the Work Package itself must be made *Available* through the off-chain Availability Protocol, which ensures that any dispute over the correctness of the Work Report can be easily objectively judged by all validators. Being off-chain this is not block-synchronized and any given Work Package make take one or more blocks to be made Available or may even fail. +Once the Work Report of a Work Package is Registered on-chain, the Work Package itself must be made *Available* through the off-chain Availability Protocol, which ensures that any dispute over the correctness of the Work Report can be easily objectively judged by all validators. Being off-chain this is not block-synchronized and any given Work Package may take one or more blocks to be made Available or may even fail. Only once a Work Report's Work Package is made Available can the processing continue with the next steps of Joining and Accumulation. Ordering requirements of Work Packages may also affect this variable latency and this is discussed later in the section **Work Package Ordering**.