Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

implementers-guide: drop WIP label in pre-checking section #7559

Merged
merged 1 commit into from
Jul 28, 2023
Merged

implementers-guide: drop WIP label in pre-checking section #7559

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions roadmap/implementers-guide/src/pvf-prechecking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down Expand Up @@ -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