Skip to content

Commit

Permalink
drafted
Browse files Browse the repository at this point in the history
  • Loading branch information
CrackTheCode016 committed Aug 7, 2023
1 parent 1a08942 commit 6051f10
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 4 deletions.
4 changes: 3 additions & 1 deletion docs/Parachain/beginner/section1/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,9 @@
title: Parachain Architecture Overview
---

Before beginning the journey to starting your parachain, it's important to realize how exactly the notion of a parachain fits into the wider architecture of Polkadot.
Before beginning the journey to starting your parachain, it's important to realize how exactly the notion of a parachain fits into the wider architecture of Polkadot.

Note that we will be using Polkadot binaries and dependencies, as indicative later, but we will be provisioning and locally running our own relay chain. We will also create and run our own parachain, which will connect to our relay chain.

import DocCardList from '@theme/DocCardList';

Expand Down
11 changes: 8 additions & 3 deletions docs/Parachain/beginner/section1/relay-chain.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The relay chain relieves the parachain of the responsibility of economic securit

## The Path of a Parablock

If you recall the diragram from Network Components, you will notice a simplified path that the parablock travels in order to be included to the relay chain:
If you recall the diagram from Network Components, you will notice a simplified path that the parablock travels in order to be included to the relay chain:

```mermaid
---
Expand Down Expand Up @@ -82,11 +82,16 @@ There are three primary stages of a parablock before it is included:
- A subset of paravalidators are selected on the relay chain to validate a particular parachain.
- The parachain's collator passes the block, considered a "Candidate" to the relay chain.
- The collator also passes the PVF, or **parachain validation function**, to the paravalidators. The PVF validates that the transitions in the candidate block is valid.
- A candidate block gets **backed** by the paravalidators.
- A candidate block gets **backed** by the paravalidators, and contains a **Proof of Validity**, or **PoV**.
- The validators on the relay chain, after a second series of checks, include the block.

For a more thorough explanation, refer to the ["The Path of a Parachain Block" by Joe Petrowski](https://polkadot.network/blog/the-path-of-a-parachain-block) and the [Polkadot Wiki](https://wiki.polkadot.network/docs/learn-parachains-protocol).

## Requirements for a Parachain

## AnV Protocol
In the list above, note the terms: **Parachain Validation Functio**n and **Proof of Validity** conc

- A Parachain Validation Function, or **PVF**, is essentially the Wasm runtime of a parachain. It defines how state is supposed to transition for that certain parachain.
- The proof of validity is generated once the state is able to be verified. The entire state of the parachain doesn't need to be verified - just the proposed state changes for that particular parablock.

In the section page, we also discussed Cumulus, a Parachain Development Kit based on FRAME and Substrate. Cumulus provides the functions needed for collators to provide the PVF and information for the proof of validity to be generated, which is required for the parachain to finalize its state on the relay chain.

0 comments on commit 6051f10

Please sign in to comment.