pezkuwichain/pezkuwi-fellows
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-fellows.git synced 2026-06-12 13:51:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update text/0031-corejam.md

Browse Source 
Co-authored-by: Sergej Sakac <73715684+Szegoo@users.noreply.github.com>
This commit is contained in:
Gavin Wood
2023-10-16 19:23:18 +01:00
committed by GitHub
parent d6bb203ae6
commit 1cb5f0d91b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
text/0031-corejam.md
+1 -1
View File
@@ -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**.