Polish mod5 content for publishing

syllabus/5-Substrate/1.0-Intro-to-Substrate_Slides.md → syllabus/5-Substrate/1-Intro-to-Substrate_Slides.md

@@ -348,6 +348,11 @@ _The way to make a protocol truly upgradeable is to design a meta-protocol that
 
 <img src="../../assets/img/5-Substrate/dev-4-1-substrate-meta.svg" />
 
+Note:
+
+In this figure, the meta-protocol, the substrate client, is not forklessly upgrade-able. It can only
+be upgraded with a fork. The WASM protocol, though, can be upgraded forklessly.
+
 ---v
 
 ### 🏦 Governance + Upgradeability
@@ -588,8 +593,6 @@ bug in it, everyone is affected.
 ## Consensus <> Runtime 🤔
 
 - Yes, consensus is not a core part of a blockchain runtime. Why?
-- Not often customized.
-<!-- .element: class="fragment" -->
 - Not part of your STF!
 <!-- .element: class="fragment" -->
 - The consensus protocol is to your runtime what HTTP is to Facebook.
@@ -996,11 +999,9 @@ exception](https://www.gnu.org/software/classpath/license.html).
 
 - Currently, the Wasm binary spec v1 is used, read more about the new version here: https://webassembly.github.io/spec/core/binary/index.html
 
-### Post Lecture Notes
+### Post Lecture Feedback
 
 - a takeaway after each section, more clear path (shawn).
-- people confuse that the client is not upgradeable AT ALL. Mention more that it is, just with forks.
-- Make the arrow bidirectional in communication paths.
 
 ---
 

syllabus/5-Substrate/2.WASM-Meta-Protocol-Slides.md → syllabus/5-Substrate/2-WASM-Meta-Protocol-Slides.md

@@ -1414,8 +1414,6 @@ SomeExternalities.execute_with(|| {
 
 ### Post Lecture Notes
 
-- Resource management (block length, weight) is dictated by the runtime.
-
 ---
 
 ## Appendix

syllabus/5-Substrate/3.Merklized-Storage_Slides.md → syllabus/5-Substrate/3-Merklized-Storage_Slides.md

@@ -424,6 +424,16 @@ size and the cost of reading/writing/encoding/decoding all these nodes.
 
 ### Base 2, Base 16, Base-26?
 
+<img style="width: 1400px;" src="../../assets/img/5-Substrate/dev-trie-backend-16-with-size.svg" />
+
+Note:
+
+Here's a different way to represent it; the nodes are bigger on the base-16 trie.
+
+---v
+
+### Base 2, Base 16, Base-26?
+
 - base-2: Small proofs, more nodes.
 - base-8: Bigger proofs, less nodes.
 
@@ -614,8 +624,6 @@ with_storage_layer(|| {
 Notes:
 
 - implement with zero-copy. So, the size of values is not so important, it is more about the number.
-- TODO: This `with_storage_layer` is currently in FRAME, but it could technically be in primitives,
-  as there is nothing frame specific about it.
 
 ---v
 
@@ -847,7 +855,9 @@ Notes:
   about what a state transition is. The runtime is the state transition function. Recall the formula
   of that, and then you will know why this is not allowed.
 
-## Post Lecture
+### Post Lecture Feedback
+
+Double check the narrative and example of the `BIG_STUFF` node. An example/exercise of some sort
+would be great, where students call a bunch of `sp_io` functions, visualize the trie, and invoke
+proof recorder, and see which pars of the trie is exactly part of the proof.
 
-From Shawn: my narrative of big_stuff still seems incorrect; 100% double check it before going any
-further.

syllabus/5-Substrate/4.x-Substrate-FRAME-Tips-Tricks-Slides.md → syllabus/5-Substrate/9-Substrate-FRAME-Tips-Tricks-Slides.md

@@ -185,8 +185,6 @@ note:
 imagine that you have a crate that has some additional features that are not always needed. You put
 that behind a feature flag called `additional-features`.
 
-TODO: feature flags should be part of the rust entrance exam.
-
 ---v
 
 ### Cargo Features: Substrate Wasm Crates
@@ -843,8 +841,6 @@ Notes:
 
 often times, in examples above, you have to use this syntax: https://doc.rust-lang.org/book/ch19-03-advanced-traits.html#fully-qualified-syntax-for-disambiguation-calling-methods-with-the-same-name
 
-TODO: we should explicitly add this to the exam as well.
-
 ---
 
 ## Implementing Traits For Tuples
@@ -1157,7 +1153,7 @@ Notes:
 - Update on defensive ops: https://github.com/paritytech/substrate/pull/12967
 - Next time, talk about making a storage struct be `<T: Config>`.
 - Cargo format
-
-TODO:
-
-- SignedExtension should technically be part of the substrate module. Integrate it in the assignment, perhaps.
+- SignedExtension should technically be part of the substrate module. Integrate it in the
+  assignment, perhaps.
+- A section about `XXXNoBound` traits.
+- A section about reading your compiler errors top to bottom, especially with an example in FRAME.

syllabus/5-Substrate/1.1-Substrate-In-The-Code_Slides.md → syllabus/5-Substrate/9-Substrate-In-The-Code_Slides.md

@@ -191,4 +191,7 @@ Simply search the trait in the rust-docs, and find the implementors!
 
 <img width="300px" rounded src="../../assets/img/5-Substrate/thats_all_folks.png" />
 
-Notes:
+Note:
+
+One important concept that is important to substrate-based chains, but is somewhat missing here is
+`chain-spec`. Make sure to read up about it in the substrate docs.

syllabus/5-Substrate/4.Substrate-Interactions_Slides.md → syllabus/5-Substrate/9-Substrate-Interactions_Slides.md

@@ -72,8 +72,6 @@ almost all external communication happens over JSPN-RPC, so let's take a closer
 
 Notes:
 
-TODO: @NukeManDan a proper solution for list with fragments would be good, see: https://github.com/hakimel/reveal.js/issues/1848
-
 recall:
 
 https://paritytech.github.io/substrate/master/sc_rpc_api/index.html
@@ -251,19 +249,6 @@ https://polkadot.js.org/docs/substrate/rpc#getstoragekey-storagekey-at-blockhash
 await api.rpc.state.getStorageSize("0x3A636F6465"),
 ```
 
-light client:
-
-TODO: needs fixing
-
-```ts
-import { ScProvider } from "@polkadot/rpc-provider/substrate-connect";
-import * as Sc from "@substrate/connect";
-
-const lightProvider = new ScProvider(Sc, Sc.WellKnownChain.polkadot);
-await lightProvider.connect();
-const lightApi = await ApiPromise.create({ lightProvider });
-```
-
 A few random other things:
 
 ```ts
@@ -294,14 +279,3 @@ Notes:
 - see "Client Libraries" here: https://project-awesome.org/substrate-developer-hub/awesome-substrate
 - https://paritytech.github.io/json-rpc-interface-spec/introduction.html
 - Full subxt guide: https://docs.rs/subxt/latest/subxt/book/index.html
-
-TODO: further assignment idea:
-
-- build a custom chain spec, then run it
-
-- Use `curl` and such to interact.
-- Connect PJS apps.
-- Write a few simple lines of TS to interact.
-- Write a few lines of Rust with SubXT to interact.
-
-Tricky, as we would be using a FRAME based runtime in order to get some metadata out of it.