From c3d81eeb5c5fe7eaa752d07967c5fff770fc7319 Mon Sep 17 00:00:00 2001 From: Chris Sosnin Date: Fri, 28 Jul 2023 19:36:58 +0400 Subject: [PATCH] drop wip label --- roadmap/implementers-guide/src/pvf-prechecking.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/roadmap/implementers-guide/src/pvf-prechecking.md b/roadmap/implementers-guide/src/pvf-prechecking.md index d4957582a153..aefe0257b05e 100644 --- a/roadmap/implementers-guide/src/pvf-prechecking.md +++ b/roadmap/implementers-guide/src/pvf-prechecking.md @@ -1,7 +1,5 @@ # PVF Pre-checking Overview -> ⚠️ This discusses a mechanism that is currently under-development. Follow the progress under [#3211][3211]. - ## Motivation Parachains' and parathreads' validation function is described by a wasm module that we refer to as a PVF. Since a PVF is a wasm module the typical way of executing it is to compile it to machine code. @@ -70,7 +68,6 @@ We define preparation as a process that: validates the consistency of the wasm b Besides pre-checking, preparation can also be triggered by execution, since a compiled artifact is needed for the execution. If an artifact already exists, execution will skip preparation. If it does do preparation, execution uses a more lenient timeout than preparation, to avoid the situation where honest validators fail on valid, pre-checked PVFs. -[3211]: https://github.com/paritytech/polkadot/issues/3211 [paras]: runtime/paras.md [pvf-runtime-api]: runtime-api/pvf-prechecking.md [pvf-prechecker-subsystem]: node/utility/pvf-prechecker.md