Deploying to gh-pages from @ 16cd7dd 🚀

Polkadot-Blockchain-Academy · May 31, 2024 · d9adb70 · d9adb70
1 parent e30d0ac
commit d9adb70
Show file tree

Hide file tree

Showing 8 changed files with 213 additions and 218 deletions.
diff --git a/current/assets/img/5-Substrate/dev-4-1-substrate-meta-version.svg b/current/assets/img/5-Substrate/dev-4-1-substrate-meta-version.svg
diff --git a/current/assets/styles/PBA-theme.css b/current/assets/styles/PBA-theme.css
@@ -160,6 +160,11 @@
   --r-hub-pink: #E6007A;
   --r-hub-lime: #D3FF33;
   --r-hub-green: #56F39A;
+
+  /* Colors used in the Polkadot-SDK Lectures */
+  --substrate-green: #25cc85ff;
+  --substrate-runtime: #bb8ba6;
+  --substrate-host: #8d3aed;
 }
 
 /* box sizing;

diff --git a/current/syllabus/6-Polkadot-SDK/Polkadot-SDK-slides.html b/current/syllabus/6-Polkadot-SDK/Polkadot-SDK-slides.html
@@ -71,8 +71,8 @@
 
 <img width="800px" rounded src="./img/multi-threaded.svg" />
 
-- Have we compromised security in any way in this model?
-</script></section><section data-markdown><script type="text/template">
+<aside class="notes"><p>Have we compromised security in any way in this model?</p>
+</aside></script></section><section data-markdown><script type="text/template">
 ### Polkadot
 
 <img width="800px" rounded src="./img/multi-threaded-dot.svg" />
@@ -144,8 +144,8 @@
 
 Substrate 🤝 FRAME
 
-Substrate: Un-opinionated primitives for building blockchains based on a WASM meta-protocol.
-FRAME: An opinionated way to build that WASM protocol/runtime/STF.
+- Substrate: Un-opinionated primitives for building blockchains based on a WASM meta-protocol.
+- FRAME: An opinionated way to build that WASM protocol/runtime/STF.
 
 <aside class="notes"><p><strong>FRAME</strong> is a subset of blockchain within Substrate that allow you to focus only on writing the
 state transition function aka. Runtime of your blockchain and not deal with the rest of the
@@ -174,17 +174,21 @@
 </script></section><section data-markdown><script type="text/template">
 ### Interoperability
 
-Polkadot's services to developers:
+Polkadot-SDK's services to developers:
 
 - Transport protocols for parachains/cores to send payloads to one
   another.
   - XCMP, HRMP, VMP, DMP 😶‍🌫️
   - As a developer you won't deal with these! 😮‍💨
 - Language to compose messages and programs and send them over.
   - XCM
+    - Shared ideas between sovereign consensus systems.
+    - Asynchronous.
 
-<aside class="notes"><p>Consensus System: Moreover, the sender and recipient of these messages can be contracts, accounts, or any other
-abstract entities within chains, not just the chain itself.</p>
+<aside class="notes"><p>On &quot;XCMP, HRMP, VMP, DMP&quot;: It is similar to building a website. You know HTTP and TCP and such
+exist, and you use them via an interface, but you don&#39;t need to know them by heart.</p>
+<p>Consensus System: Moreover, the sender and recipient of these messages can be contracts, accounts, or any
+other abstract entities within chains, not just the chain itself.</p>
 <p>Async and Sync: Disjoint consensus systems are in principle[^1] asynchronous by nature. This is an
 important concept to keep in mind.</p>
 <p>[^1]:

diff --git a/current/syllabus/6-Polkadot-SDK/Substrate/1-Intro-to-Substrate-slides.html b/current/syllabus/6-Polkadot-SDK/Substrate/1-Intro-to-Substrate-slides.html
@@ -70,6 +70,21 @@
 can create sovereign chains with substrate, or Polkadot Parachains, or more hybrid things. More on
 this when you learn about Substrate&#39;s role in the Polkadot ecosystem.</p>
 <p>Figure: <a href="https://www.youtube.com/watch?v=0IoUZdDi5Is">https://www.youtube.com/watch?v=0IoUZdDi5Is</a></p>
+</aside></script></section><section data-markdown><script type="text/template">
+### Why Substrate?
+
+#### 💭 An update in 2024 💭
+
+🧐 Multi-chain vs. Multi-shard 🧐
+
+<aside class="notes"><p>Polkadot led the way since 2016 to convince the world that the future is multi-chain.</p>
+<p>Cosmos tried to replicate the same without shared security.</p>
+<p>ETH is now doing something similar, with a Rollup-Centric roadmap.</p>
+<p>Interestingly, Polkadot is now arguing that the future is not necessarily multi-chain, but rather
+multi-shard. In that, there needs to be a sharded system, with a high degree of flexibility to
+schedule those shards. &quot;Multi-chain&quot; is merely one manifestation of a multi-shard system, which is
+actually not so flexible. We are now striving to make the multi-chain Polkadot more flexible, which
+is what JAM is going to be.</p>
 </aside></script></section></section><section ><section data-markdown><script type="text/template">
 ## Core Philosophies of Substrate 💭
 
@@ -275,8 +290,10 @@
 </aside></script></section><section data-markdown><script type="text/template">
 ### 🏦 Governance + Upgradeability
 
-_The way to make a protocol truly upgradeable is to design a meta-protocol._
-</script></section><section data-markdown><script type="text/template">
+<img src="../../../assets/img/5-Substrate/dev-4-1-substrate-meta-substrate.svg" />
+
+<aside class="notes"><p>This is very similar to treating your own runtime as a smart contract.</p>
+</aside></script></section><section data-markdown><script type="text/template">
 ### 🏦 Governance + Upgradeability
 
 <img src="../../../assets/img/5-Substrate/dev-4-1-substrate-meta.svg" />
@@ -286,10 +303,8 @@
 </aside></script></section><section data-markdown><script type="text/template">
 ### 🏦 Governance + Upgradeability
 
-<img src="../../../assets/img/5-Substrate/dev-4-1-substrate-meta-substrate.svg" />
-
-<aside class="notes"><p>This is very similar to treating your own runtime as a smart contract.</p>
-</aside></script></section><section data-markdown><script type="text/template">
+_The way to make a protocol truly upgradeable is to design a (fixed) meta-protocol._
+</script></section><section data-markdown><script type="text/template">
 ### 🏦 Governance + Upgradeability
 
 - Meta-protocol?
@@ -308,15 +323,25 @@
 <pba-col center>
 <h3 style="color: var(--substrate-runtime); top: 0"> Runtime (Protocol) </h3>
 
-- Application logic
-- Wasm (maybe **FRAME**)
-- Stored as a part of your chain state
+- Application logic aka. How we execute block
+- Stored as a part of your chain state as a WASM Blob
+- Upgradeable
 - Also known as: STF
 
 </pba-col>
 
 <pba-col center>
-<h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
+
+<img width="600px" src="../../../assets/img/5-Substrate/dev-4-1-substrate.svg" />
+
+</pba-col>
+</pba-cols>
+</script></section><section data-markdown><script type="text/template">
+#### Substrate (simplified) Architecture
+
+<pba-cols>
+<pba-col center>
+<h3 style="color: var(--substrate-host); top: 0"> Fixed Node (Meta-protocol) </h3>
 
 - Native Binary
 - Executes the Wasm runtime
@@ -325,6 +350,12 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
 
 </pba-col>
 
+<pba-col center>
+
+<img width="600px" src="../../../assets/img/5-Substrate/dev-4-1-substrate.svg" />
+
+</pba-col>
+
 </pba-cols>
 </script></section></section><section ><section data-markdown><script type="text/template">
 ## Positive Consequences of _Wasm_ Runtime 🔥
@@ -399,32 +430,6 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
 <p><a href="https://forum.polkadot.network/t/eliminating-pre-dispatch-weight/400">https://forum.polkadot.network/t/eliminating-pre-dispatch-weight/400</a></p>
 <p><a href="https://forum.polkadot.network/t/announcing-polkavm-a-new-risc-v-based-vm-for-smart-contracts-and-possibly-more/3811/32">https://forum.polkadot.network/t/announcing-polkavm-a-new-risc-v-based-vm-for-smart-contracts-and-possibly-more/3811/32</a></p>
 </aside></script></section></section><section ><section data-markdown><script type="text/template">
-## State of Light Client/Nodes
-
-- Node that follows headers, therefore knows state roots and can ask for state-proofs to do more.
-
-<aside class="notes"><p>Establish that it is merely an alternative node implementation.</p>
-</aside></script></section><section data-markdown><script type="text/template">
-### State of Light Clients
-
-<img src="../../../assets/img/5-Substrate/dev-4-1-smoldot.svg" />
-
-<aside class="notes"><p>What was a light client? follows only block headers, therefore knows state roots, and a few other
-pieces of information, others send it state proofs if it wishes to do more.</p>
-<p>SMOLDOT is not exactly a substrate client. It is mainly designed to work with Polkadot. But with
-minimal tweaks, you could make it work for more substrate based chains.</p>
-<p>This has to do with the fact that consensus and a few other bits of the client and runtime are not
-100% independent. For example, GRANDPA has a pallet on the runtime side, but is mostly in the
-client. Now, a client that is configured with GRANDPA can only work with runtimes that are also
-configured with GRANDPA.</p>
-</aside></script></section><section data-markdown><script type="text/template">
-### State of Light Clients
-
-<img style="width: 800px;" src="../../../assets/img/5-Substrate/dev-4-1-smoldot-browser.svg" />
-
-<aside class="notes"><p>Similarly it is dead simple to embed smoldot in mobile etc.</p>
-<p>Separate lecture on this later.</p>
-</aside></script></section></section><section ><section data-markdown><script type="text/template">
 ## Communication Paths
 
 <img style="width: 1400px" src="../../../assets/img/5-Substrate/dev-4-1-comms.svg" />
@@ -526,30 +531,6 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
 </script></section><section data-markdown><script type="text/template">
 ### Substrate and Smart Contracts
 
-> SMOLDOT is syncing a chain who's runtime is executing wasm contracts.
-
-Question: How many nested Wasm blobs are executing one another?
-</script></section><section data-markdown><script type="text/template">
-### Substrate and Smart Contracts
-
-<pba-cols>
-<pba-col center>
-
-<img style="width: 600px;" src="https://media.tenor.com/Oc4nf8N08jIAAAAM/mind-blow-galaxy.gif" />
-
-</pba-col>
-<pba-col>
-
-- The browser is executing:
-- a Wasm blob (SMOLDOT in extension)
-- that executes a Wasm blob (runtime)
-- that executes a Wasm blob (contract)
-
-</pba-col>
-</pba-cols>
-</script></section><section data-markdown><script type="text/template">
-### Substrate and Smart Contracts
-
 - So when should you write with a smart contract, and when a Runtime (FRAME)?
 
 <aside class="notes"><p><a href="https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/reference_docs/runtime_vs_smart_contract/index.html">https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/reference_docs/runtime_vs_smart_contract/index.html</a></p>
@@ -562,7 +543,7 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
 <p>Also, a contract usually depends on a token for gas, while a runtime can be in principle token-less
 fee-less.</p>
 </aside></script></section></section><section  data-markdown><script type="text/template">
-## Technical Freedom vs Ease
+## Development Options
 
 <img style="width: 1000px;" src="../../../assets/img/5-Substrate/dev-4-1-freedom.svg" />
 
@@ -743,8 +724,7 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
   - **Rust**, **Generic Design**, **Upgradeability/Governance**
 - Positive and negative consequences of Wasm
 - Substrate next to Polkadot and other chains.
-- Substrate for Smart Contracts.
-- Light Nodes/Clients.
+- Substrate and Smart Contracts.
 - Node / Runtime architecture
 - State Transition Deep Dive -> Forkless Upgrade
 </script></section><section data-markdown><script type="text/template">
@@ -777,7 +757,7 @@ <h3 style="color: var(--substrate-host); top: 0"> Node (Meta-protocol) </h3>
 
 #### Track: Aux Lecture
 
-- Tx Pool (Kian)
+- Tx Pool
 - Interacting with Substrate
 - SCALE Codec
 
@@ -842,8 +822,12 @@ <h3 id="post-lecture-feedback">Post Lecture Feedback</h3>
 <ul>
 <li>a takeaway after each section, more clear path (shawn).</li>
 </ul>
-</aside></script></section><section ><section data-markdown><script type="text/template">
-## Appendix: More Diagrams of Substrate and Polkadot
+</aside></script></section><section  data-markdown><script type="text/template">
+## Appendix
+
+Content that is not covered, but is relevant.
+</script></section><section ><section data-markdown><script type="text/template">
+### More Diagrams of Substrate and Polkadot
 
 <aside class="notes"><p>I made these figures recently to explain the relationship between Substrate, Cumulus and Polkadot.
 They use the most generic term for client and runtime, namely &quot;Host&quot; and &quot;STF&quot; respectively.</p>
@@ -895,6 +879,56 @@ <h3 id="post-lecture-feedback">Post Lecture Feedback</h3>
 
 - Any language that can compile to Wasm and exposes a fixed set of functions, to be used by the client.
 - ... But, of course, Substrate comes with a framework to make this developer-friendly, **FRAME™️**.
+</script></section></section><section ><section data-markdown><script type="text/template">
+## State of Light Client/Nodes
+
+- Node that follows headers, therefore knows state roots and can ask for state-proofs to do more.
+
+<aside class="notes"><p>Establish that it is merely an alternative node implementation.</p>
+</aside></script></section><section data-markdown><script type="text/template">
+### State of Light Clients
+
+<img src="../../../assets/img/5-Substrate/dev-4-1-smoldot.svg" />
+
+<aside class="notes"><p>What was a light client? follows only block headers, therefore knows state roots, and a few other
+pieces of information, others send it state proofs if it wishes to do more.</p>
+<p>SMOLDOT is not exactly a substrate client. It is mainly designed to work with Polkadot. But with
+minimal tweaks, you could make it work for more substrate based chains.</p>
+<p>This has to do with the fact that consensus and a few other bits of the client and runtime are not
+100% independent. For example, GRANDPA has a pallet on the runtime side, but is mostly in the
+client. Now, a client that is configured with GRANDPA can only work with runtimes that are also
+configured with GRANDPA.</p>
+</aside></script></section><section data-markdown><script type="text/template">
+### State of Light Clients
+
+<img style="width: 800px;" src="../../../assets/img/5-Substrate/dev-4-1-smoldot-browser.svg" />
+
+<aside class="notes"><p>Similarly it is dead simple to embed smoldot in mobile etc.</p>
+<p>Separate lecture on this later.</p>
+</aside></script></section><section data-markdown><script type="text/template">
+### Substrate and Smart Contracts
+
+> SMOLDOT is syncing a chain who's runtime is executing wasm contracts.
+
+Question: How many nested Wasm blobs are executing one another?
+</script></section><section data-markdown><script type="text/template">
+### Substrate and Smart Contracts
+
+<pba-cols>
+<pba-col center>
+
+<img style="width: 600px;" src="https://media.tenor.com/Oc4nf8N08jIAAAAM/mind-blow-galaxy.gif" />
+
+</pba-col>
+<pba-col>
+
+- The browser is executing:
+- a Wasm blob (SMOLDOT in extension)
+- that executes a Wasm blob (runtime)
+- that executes a Wasm blob (contract)
+
+</pba-col>
+</pba-cols>
 </script></section></section>
     </article>
   </main>