From eb93fdafd4b8b8c4d5a68c30e9b51ff270cf4792 Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Fri, 13 Oct 2023 14:37:59 +0100 Subject: [PATCH] Update text/0031-corejam.md Co-authored-by: gupnik <17176722+gupnik@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 283e505..2829ace 100644 --- a/text/0031-corejam.md +++ b/text/0031-corejam.md @@ -173,7 +173,7 @@ The `code_hash` of the Authorizer is assumed to be the hash of some code accessi fn is_authorized(param: &AuthParam, package: &WorkPackage, core_index: CoreIndex) -> bool; ``` -If the `is_authorized` function overruns the system-wide limit or panicks on some input, it is considered equivalent to returning `false`. While it is mostly stateless (e.g. isolated from any Relay-chain state) it is provided with a `context` parameter in order to give information about a recent Relay-chain block. This allows it to be provided with a concise proof over some recent state Relay-chain state. +If the `is_authorized` function overruns the system-wide limit or panicks on some input, it is considered equivalent to returning `false`. While it is mostly stateless (e.g. isolated from any Relay-chain state) it is provided with a `context` parameter in order to give information about a recent Relay-chain block. This allows it to be provided with a concise proof over some recent Relay-chain state. A single `Authorizer` value is associated with the index of the Core at a particular Relay-chain block and limits in some way what Work Packages may be legally processed by that Core.