Deploying to gh-pages from @ 54335ae 🚀

current/syllabus/7-Polkadot/1-decisions-of-polkadot-slides.html

@@ -135,35 +135,25 @@
 
 What are the type 1 decisions which define Polkadot?
 </script></section><section  data-markdown><script type="text/template">
-## Wasm
+## Parallel Execution
 
-<div class="grid grid-cols-3">
-
-<div>
-
-<img style="width: 400px;" src="../../assets/img/0-Shared/logo/webassembly-blue.png" />
-
-</div>
-
-<div class="col-span-2">
-
-WebAssembly is the backbone of Polkadot. It is a fast, safe, and open meta-protocol which powers all of the state transitions of our ecosystem.
+Polkadot scales through parallelization.
 
-It standardizes how chains execute, sandboxes that execution for improved security, and allows teams to build on Polkadot using any language that can be compiled into Wasm.
+Polkadot provides parallelized execution using parallel execution cores.
 
-</div>
+<img style="width: 1000px;" src="../../assets/img/7-Polkadot/decisions/exotic-scheduling.png" />
 
-</div>
+Execution cores allows Polkadot to provide blockspace-as-a-service, and are designed to work with any kind of Web3 application.
 </script></section><section  data-markdown><script type="text/template">
-## Sharding
+## Data Sharding
 
 <div class="grid grid-cols-2">
 
 <div>
 
-Polkadot scales primarily by parallelizing execution on separate data shards.
+Polkadot is able to do parallel execution because it splits up data on its network into separate data shards.
 
-These parallel chains (shards) are called Parachains.
+Today, parallel chains (shards) are called Parachains.
 
 </div>
 
@@ -195,23 +185,25 @@
 
 </div>
 </script></section><section  data-markdown><script type="text/template">
-## Interoperability
+## Execution Meta-Protocol
 
-<div class="grid grid-cols-2">
+<div class="grid grid-cols-3">
 
 <div>
 
-Individual application chains will inherently lack the ability to provide a full suite of optimized solutions for end users.
-
-Interoperability allows parachains to work together to complete, complex end-to-end scenarios.
+<img style="width: 400px;" src="../../assets/img/0-Shared/logo/webassembly-blue.png" />
 
 </div>
 
-<div>
+<div class="col-span-2">
 
-<img style="height: 500px;" src="../../assets/img/7-Polkadot/xcmp-2.svg" />
+To provide heterogenous sharded execution we need a fast, safe, and open meta-protocol to power all of the state transitions in our ecosystem.
 
-A visual of XCMP channels between Parachains.
+Today we use Wasm.
+
+It standardizes how Web3 applications execute and sandboxes that execution for improved security.
+
+It also allows teams to build on Polkadot using any language that can be compiled into Wasm.
 
 </div>
 
@@ -223,9 +215,11 @@
 
 <div>
 
-An often overlooked problem is economic scaling of the entire blockchain ecosystem.
+Blockspace is the capacity of a blockchain to commit and finalize operations.
 
-Polkadot is unique in that it provides all connected parachains with the same security guarantees as the Relay Chain itself.
+An often overlooked problem is the economic scaling need to provide high quality blockspace.
+
+Polkadot is unique in that it provides blockspace to other Web3 applications with the same security guarantees as Polkadot itself.
 
 </div>
 
@@ -237,16 +231,31 @@
 
 </div>
 
-<aside class="notes"><p>Security in proof-of-stake networks depends on economics, so there can only exist a limited amount of security in the world because economic value is, by definition, limited. As the number of blockchains increases due to scaling issues on single chains, their economic value — and therefore their security — gets spread out over multiple chains, leaving each one weaker than before.</p>
+<aside class="notes"><p>Learn more about blockspace: <a href="https://www.rob.tech/blog/polkadot-blockspace-over-blockchains/">https://www.rob.tech/blog/polkadot-blockspace-over-blockchains/</a></p>
+<p>Security in proof-of-stake networks depends on economics, so there can only exist a limited amount of security in the world because economic value is, by definition, limited. As the number of blockchains increases due to scaling issues on single chains, their economic value — and therefore their security — gets spread out over multiple chains, leaving each one weaker than before.</p>
 <p>Polkadot introduces a shared security model so that chains can interact with others while knowing full well that their interlocutors have the same security guarantees as their own chain. Bridge-based solutions — where each chain handles its own security — force the receiver to trust the sender. Polkadot’s security model provides the necessary guarantees to make cross-chain messages meaningful without trusting the security of the sender.</p>
 </aside></script></section><section  data-markdown><script type="text/template">
-## Execution Cores
+## Interoperability
 
-Polkadot's Shared Security is powered through the creation and allocation of execution cores.
+<div class="grid grid-cols-2">
 
-<img style="width: 1000px;" src="../../assets/img/7-Polkadot/decisions/exotic-scheduling.png" />
+<div>
+
+Individual application chains will inherently lack the ability to provide a full suite of optimized solutions for end users.
+
+Interoperability allows parachains to work together to complete, complex end-to-end scenarios.
+
+</div>
 
-Execution cores provide blockspace-as-a-service, and are designed to work with any kind of consensus system.
+<div>
+
+<img style="height: 500px;" src="../../assets/img/7-Polkadot/xcmp-2.svg" />
+
+A visual of XCMP channels between Parachains.
+
+</div>
+
+</div>
 </script></section><section  data-markdown><script type="text/template">
 ## Trust-Free Interactions
 
@@ -381,7 +390,7 @@
 </script></section><section  data-markdown><script type="text/template">
 ## Parachains
 
-Polkadot was designed around Parachains, but the exact meaning and manifestation of a Parachain is evolving.
+Polkadot was originally designed around Web3 applications in the form of Parachains, but this categorization is evolving.
 
 <div class="grid grid-cols-2">
 
@@ -402,7 +411,7 @@
 <br />
 
 - Originally, parachains would be long term applications-chains.
-- On-Demand Parachains (formerly parathreads) changed that viewpoint to also include chains which can spin-up and spin-down at will.
+- Services and Agile Coretime changed that viewpoint to also include applications that can spin-up and spin-down at will.
 - The future protocol will have even more exotic core scheduling and even more agile core usage, all because the type 1 decision around parachains is actually **execution cores**.
 
 <aside class="notes"><ul>
@@ -464,14 +473,6 @@
 
 The protocol has been actively evolving over time, making it more performant and accessible to users, for example with nomination pools.
 </script></section><section  data-markdown><script type="text/template">
-## SASSAFRAS
-
-While hybrid consensus is a type 1 decision, the underlying protocols can continue to evolve, such as from BABE to SASSAFRAS.
-
-> Semi Anonymous Sortition of Staked Assignees For Fixed-time Rhythmic Assignment of Slots
-
-An extension of BABE and acts as a constant-time block production protocol. This approach tries to address the shortcomings of BABE by ensuring that exactly one block is produced with time-constant intervals. The protocol utilizes zk-SNARKs to construct a ring-VRF and is a work in progress.
-</script></section><section  data-markdown><script type="text/template">
 ## OpenGov
 
 The specifics of Polkadot's on-chain governance system has changed multiple times in its history.
@@ -494,6 +495,55 @@
 
 An invention machine.
 </script></section><section  data-markdown><script type="text/template">
+# JAM
+</script></section><section  data-markdown><script type="text/template">
+## What is JAM?
+
+JAM is the next evolution of the Polkadot protocol.
+
+<img style="width: 600px;" src="../../assets/img/7-Polkadot/decisions/jam-pen-polkadot.png" />
+
+The JAM chain will be the successor to the existing Polkadot Relay chain.
+
+JAM will provide all the functionality of Polkadot v1, but also provide a more flexible foundation on which to build Web3 Applications.
+</script></section><section  data-markdown><script type="text/template">
+## The Decisions of JAM
+
+<div class="grid grid-cols-2">
+<div>
+
+**Unchanged**
+
+- The Philosophies of Polkadot
+- The Goals of Polkadot
+  - Parallel Execution and Heterogenous Sharding
+  - Shared Security
+  - Interoperability
+
+</div>
+
+<div>
+
+**Changed**
+
+- Upgradability of the Core Protocol
+  - Substrate -> JAM Chain
+- Services (as a superset of Parachains)
+- Wasm -> PolkaVM (RISC-V)
+- Synchronous Communication Capabilities
+
+</div>
+</script></section><section  data-markdown><script type="text/template">
+## Is JAM a new protocol?
+
+JAM is certainly the next evolution of the Polkadot protocol.
+
+- Some things have explicitly changed.
+- But the problem we are trying to solve is the same.
+- And almost all of the same technology is being used to solve it.
+
+### JAM is Polkadot.
+</script></section><section  data-markdown><script type="text/template">
 # So what is Polkadot?
 </script></section><section  data-markdown><script type="text/template">
 ## Polkadot is...