From e32333dfc4626ef16417f524e76bdb6dcd3d3652 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Wed, 18 Oct 2023 23:40:18 +0100 Subject: [PATCH] Update text/0031-corejam.md Co-authored-by: Oliver Tale-Yazdi --- 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 e272b32..8ab6523 100644 --- a/text/0031-corejam.md +++ b/text/0031-corejam.md @@ -150,7 +150,7 @@ The first two stages of the CoreJam process are *Collect* and *Refine*. *Collect Collection is the means of a Validator Group member attaining a Work Package which is authorized to be performed on their assigned Core at the current time. Authorization is a prerequisite for a Work Package to be included on-chain. Computation of Work Packages which are not Authorized is not rewarded. Incorrectly attesting that a Work Package is authorized is a disputable offence and can result in substantial punishment. -On arrival of a Work Package, after the initial decoding, a first check is the that the `context` field is valid. This must reference a header hash of a known block which may yet be finalized and the additional fields must correspond to the data of that block. +On arrival of a Work Package, after the initial decoding, a first check is that the `context` field is valid. This must reference a header hash of a known block which may yet be finalized and the additional fields must correspond to the data of that block. There are two kinds of Authorization corresponding to the two kinds of Coretime which are sold by Polkadot (see RFC#0001). An Authorization for usage of Instantaneous Coretime consists of a self-contained Signature of an account which own enough Instantaneous Coretime Credit in order to purchase a block of Coretime at the current rate signing a payload of the Work Package hash.