substrate module @ pba3 (#749)

Polkadot-Blockchain-Academy · Jul 24, 2023 · 1b834cb · 1b834cb
1 parent 08f10f3
commit 1b834cb
Show file tree

Hide file tree

Showing 101 changed files with 9,885 additions and 4,341 deletions.
diff --git a/assets/img/5-Substrate/dev-4-1-contracts.svg b/assets/img/5-Substrate/dev-4-1-contracts.svg
diff --git a/assets/img/5-Substrate/dev-4-1-forkless-1.svg b/assets/img/5-Substrate/dev-4-1-forkless-1.svg
diff --git a/assets/img/5-Substrate/dev-4-1-forkless-2.svg b/assets/img/5-Substrate/dev-4-1-forkless-2.svg
diff --git a/assets/img/5-Substrate/dev-4-1-json.svg b/assets/img/5-Substrate/dev-4-1-json.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state-code-next.pdf b/assets/img/5-Substrate/dev-4-1-state-code-next.pdf
diff --git a/assets/img/5-Substrate/dev-4-1-state-code-next.svg b/assets/img/5-Substrate/dev-4-1-state-code-next.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state-code.svg b/assets/img/5-Substrate/dev-4-1-state-code.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state-database.svg b/assets/img/5-Substrate/dev-4-1-state-database.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state-def.svg b/assets/img/5-Substrate/dev-4-1-state-def.svg
diff --git a/...img/5-Substrate/dev-4-1-state-opaqueu.svg → .../img/5-Substrate/dev-4-1-state-opaque.svg b/...img/5-Substrate/dev-4-1-state-opaqueu.svg → .../img/5-Substrate/dev-4-1-state-opaque.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state-transition-def.svg b/assets/img/5-Substrate/dev-4-1-state-transition-def.svg
diff --git a/assets/img/5-Substrate/dev-4-1-state.svg b/assets/img/5-Substrate/dev-4-1-state.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-meta-substrate.svg b/assets/img/5-Substrate/dev-4-1-substrate-meta-substrate.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-meta-version.svg b/assets/img/5-Substrate/dev-4-1-substrate-meta-version.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-meta.svg b/assets/img/5-Substrate/dev-4-1-substrate-meta.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-monol-2.svg b/assets/img/5-Substrate/dev-4-1-substrate-monol-2.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-monol.svg b/assets/img/5-Substrate/dev-4-1-substrate-monol.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-new-1.svg b/assets/img/5-Substrate/dev-4-1-substrate-new-1.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-new-2.svg b/assets/img/5-Substrate/dev-4-1-substrate-new-2.svg
diff --git a/assets/img/5-Substrate/dev-4-1-substrate-new-3.svg b/assets/img/5-Substrate/dev-4-1-substrate-new-3.svg
diff --git a/assets/img/5-Substrate/dev-4-3-author-builder.svg b/assets/img/5-Substrate/dev-4-3-author-builder.svg
diff --git a/assets/img/5-Substrate/dev-4-3-author-pool.svg b/assets/img/5-Substrate/dev-4-3-author-pool.svg
diff --git a/assets/img/5-Substrate/dev-4-3-full-comm.svg b/assets/img/5-Substrate/dev-4-3-full-comm.svg
diff --git a/assets/img/5-Substrate/dev-4-3-full.svg b/assets/img/5-Substrate/dev-4-3-full.svg
diff --git a/assets/img/5-Substrate/dev-4-3-import.svg b/assets/img/5-Substrate/dev-4-3-import.svg
diff --git a/assets/img/5-Substrate/dev-4-3-pruning-1.svg b/assets/img/5-Substrate/dev-4-3-pruning-1.svg
diff --git a/assets/img/5-Substrate/dev-4-3-pruning-2.svg b/assets/img/5-Substrate/dev-4-3-pruning-2.svg
diff --git a/assets/img/5-Substrate/dev-4-3-pruning-3.svg b/assets/img/5-Substrate/dev-4-3-pruning-3.svg
diff --git a/assets/img/5-Substrate/dev-4-3-pruning-4.svg b/assets/img/5-Substrate/dev-4-3-pruning-4.svg
diff --git a/assets/img/5-Substrate/dev-4-json.svg b/assets/img/5-Substrate/dev-4-json.svg
diff --git a/assets/img/5-Substrate/dev-kv-backend.svg b/assets/img/5-Substrate/dev-kv-backend.svg
diff --git a/assets/img/5-Substrate/dev-storage-1.svg b/assets/img/5-Substrate/dev-storage-1.svg
diff --git a/assets/img/5-Substrate/dev-storage-2.svg b/assets/img/5-Substrate/dev-storage-2.svg
diff --git a/assets/img/5-Substrate/dev-storage-3.svg b/assets/img/5-Substrate/dev-storage-3.svg
diff --git a/assets/img/5-Substrate/dev-storage-4.svg b/assets/img/5-Substrate/dev-storage-4.svg
diff --git a/assets/img/5-Substrate/dev-storage-full.svg b/assets/img/5-Substrate/dev-storage-full.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-proof-fat-fix.svg b/assets/img/5-Substrate/dev-trie-backend-proof-fat-fix.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-proof-fat.svg b/assets/img/5-Substrate/dev-trie-backend-proof-fat.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-proof.svg b/assets/img/5-Substrate/dev-trie-backend-proof.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-simple.svg b/assets/img/5-Substrate/dev-trie-backend-simple.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-walk-0.svg b/assets/img/5-Substrate/dev-trie-backend-walk-0.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-walk-1.svg b/assets/img/5-Substrate/dev-trie-backend-walk-1.svg
diff --git a/assets/img/5-Substrate/dev-trie-backend-walk-full.svg b/assets/img/5-Substrate/dev-trie-backend-walk-full.svg
diff --git a/assets/img/5-Substrate/thats_all_folks copy.png b/assets/img/5-Substrate/thats_all_folks copy.png
diff --git a/assets/img/5-Substrate/trie-backend-simple-simple.svg b/assets/img/5-Substrate/trie-backend-simple-simple.svg
diff --git a/assets/img/6-FRAME/thats_all_folks.png b/assets/img/6-FRAME/thats_all_folks.png
diff --git a/syllabus/3-Blockchain/13-Forks_slides.md b/syllabus/3-Blockchain/13-Forks_slides.md
@@ -22,6 +22,7 @@ revealOptions:
 # Landscape
 
 ---v
+
 ## Landscape
 
 #### Ideal World
@@ -32,6 +33,7 @@ In an ideal world blockchains would look like this:
 <img style="width: 800px" src="../../assets/img/3-Blockchain/forks/no_fork.drawio.svg" />
 
 ---v
+
 ## Landscape
 
 #### Real World
@@ -43,6 +45,7 @@ Things don't always go according to plan:
 <img style="width: 800px" src="../../assets/img/3-Blockchain/forks/fork_small.drawio.svg" />
 
 ---v
+
 ## Landscape
 
 #### Chaotic Real World
@@ -134,6 +137,7 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 800px" src="../../assets/img/3-Blockchain/forks/BTC_block.drawio.svg" />
 
@@ -142,15 +146,16 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 300px" src="../../assets/img/3-Blockchain/forks/BTC_header.drawio.svg" />
 
-
 ---v
 
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 500px" src="../../assets/img/3-Blockchain/forks/BTC_header_constraints.drawio.svg" />
 
@@ -159,6 +164,7 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 500px" src="../../assets/img/3-Blockchain/forks/validity_set.drawio.svg" />
 
@@ -167,6 +173,7 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 500px" src="../../assets/img/3-Blockchain/forks/universal_set.drawio.svg" />
 
@@ -175,6 +182,7 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 500px" src="../../assets/img/3-Blockchain/forks/validity_set_old.drawio.svg" />
 
@@ -183,10 +191,12 @@ Why? Forks in the same category will exhibit similar behaviour and will require
 ## Consensus Forks
 
 #### _Validity Set_
+
 <br>
 <img style="width: 500px" src="../../assets/img/3-Blockchain/forks/validity_set_new.drawio.svg" />
 
 ---v
+
 ## Consensus Forks
 
 #### _Validity Set_
@@ -275,7 +285,6 @@ Is decreasing or increasing blocksize a soft fork?
     </pba-col>
 </pba-cols>
 
-
 ---v
 
 ## Fork Categorisation
@@ -364,6 +373,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 ---
+
 # Hard Forks
 
 ---v
@@ -376,6 +386,7 @@ Is decreasing or increasing blocksize a soft fork?
 <img style="width: 800px" src="../../assets/img/3-Blockchain/forks/fork_family_hard.drawio.svg" />
 
 ---v
+
 ## Fork Categorisation
 
 #### _Hard Forks_
@@ -396,6 +407,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 ---v
+
 ## Fork Categorisation
 
 #### _Hard Forks_
@@ -418,6 +430,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 ---v
+
 ## Fork Categorisation
 
 #### _Hard Forks_
@@ -433,6 +446,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 ---v
+
 ## Fork Categorisation
 
 #### _Hard Forks_
@@ -482,6 +496,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 ---v
+
 ## Fork Categorisation
 
 #### _Full Forks_
@@ -523,7 +538,6 @@ Is decreasing or increasing blocksize a soft fork?
 
 ## Summary
 
-
 <pba-cols>
     <pba-col>
 		<img style="width: 400px" src="../../assets/img/3-Blockchain/forks/soft_forks_s50.drawio.svg" />
@@ -541,6 +555,7 @@ Is decreasing or increasing blocksize a soft fork?
 </pba-cols>
 
 Notes:
+
 - Bitcoin cash pivot from hard to full because they didn't have enough HP.
 - Soft are often preferred for changes because with >50%HP they do not fracture the community (BTC community logic)
 - Hard can be preferred as they seem to better represent minorities. If some people don't agree with the majority they naturally fork off and are not peer pressured to follow (ETH community logic)
@@ -552,4 +567,3 @@ Notes:
 ---
 
 <img style="width: 1800px" src="../../assets/img/3-Blockchain/forks/forks.drawio.svg" />
-