From 8b321a7a3d3b3cf70ce4f2992b3e636e3f9a5d71 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Wed, 18 Oct 2023 23:40:05 +0100 Subject: [PATCH 1/3] 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 d10f49a..e272b32 100644 --- a/text/0031-corejam.md +++ b/text/0031-corejam.md @@ -144,7 +144,7 @@ Finally, at some point later still `T+r+i+a+o`, the Results of the Work Package ### Collect-Refine -The first two stages of the CoreJam process are *Collect* and *Refine*. *Collect* refers to the collection and authorization of Work Packages (collections of items together with an authorization) to utilize a Polkadot Core. *Refine* refers to the performance of computation according to the Work Packages in order to yield a *Work Result*. Finally, each Validator Group member attests to a Work Package yielding a set of Work Results and these Attestations form the basis for bringing the Results on-chain and integrating them into the Polkadot (and in particular the Work Class's) state which happens in the following stages. +The first two stages of the CoreJam process are *Collect* and *Refine*. *Collect* refers to the collection and authorization of Work Packages (collections of items together with an authorization) to utilize a Polkadot Core. *Refine* refers to the performance of computation according to the Work Packages in order to yield *Work Results*. Finally, each Validator Group member attests to a Work Package yielding a series of Work Results and these Attestations form the basis for bringing the Results on-chain and integrating them into the Polkadot (and in particular the Work Class's) state which happens in the following stages. #### Collection and `is_authorized` From e32333dfc4626ef16417f524e76bdb6dcd3d3652 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Wed, 18 Oct 2023 23:40:18 +0100 Subject: [PATCH 2/3] 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. From e33e467400419621ca5f47e359d294bef6674822 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Wed, 18 Oct 2023 23:40:33 +0100 Subject: [PATCH 3/3] 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 8ab6523..2d97899 100644 --- a/text/0031-corejam.md +++ b/text/0031-corejam.md @@ -152,7 +152,7 @@ Collection is the means of a Validator Group member attaining a Work Package whi 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. +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 owns enough Instantaneous Coretime Credit in order to purchase a block of Coretime at the current rate by signing a payload of the Work Package hash. RcVGs run the risk of a credit owner not having the credit at the point of eventual payment (in the Join stage, later), in which case the RcVG will not be rewarded. Credit may never be withdrawn, therefore RcVGs can safely accept a block if and only if the Credit account contains a balance of at least the product of the number of Cores assigned to IC, the price per IC core per block and the number of blocks behind the head of the finalized chain which the RcVG currently may be.