complete Consensus Topic references

.obsidian/graph.json

@@ -30,8 +30,8 @@
   "collapse-forces": false,
   "centerStrength": 0,
   "repelStrength": 20,
-  "linkStrength": 1,
+  "linkStrength": 0.876960037198729,
   "linkDistance": 500,
-  "scale": 0.10689967036573943,
+  "scale": 0.09848280266864441,
   "close": true
 }

.obsidian/hotkeys.json

@@ -51,5 +51,14 @@
       ],
       "key": "P"
     }
+  ],
+  "insert-current-date": [
+    {
+      "modifiers": [
+        "Alt",
+        "Mod"
+      ],
+      "key": " "
+    }
   ]
 }

.obsidian/plugins/obsidian-discordrpc/manifest.json

@@ -0,0 +1,9 @@
+{
+  "id": "obsidian-discordrpc",
+  "name": "Discord Rich Presence",
+  "version": "1.5.0",
+  "description": "Update your Discord Status to show your friends what you are working on in Obsidian. With Discord Rich Presence.",
+  "author": "Luke Leppan",
+  "authorUrl": "https://lukeleppan.com",
+  "isDesktopOnly": false
+}

.obsidian/workspace

@@ -4,12 +4,12 @@
     "type": "split",
     "children": [
       {
-        "id": "bc3b95f36f9e4d7b",
+        "id": "58828f807fb5587f",
         "type": "leaf",
         "state": {
           "type": "markdown",
           "state": {
-            "file": "README.md",
+            "file": "pages/Project Waku.md",
             "mode": "source",
             "backlinks": false,
             "source": false
@@ -71,7 +71,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "README.md",
+                "file": "pages/Project Waku.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -100,17 +100,17 @@
     "width": 300,
     "collapsed": true
   },
-  "active": "bc3b95f36f9e4d7b",
+  "active": "58828f807fb5587f",
   "lastOpenFiles": [
-    "README.md",
+    "pages/Project Waku.md",
-    "pages/README.md",
+    "pages/Set of Implementations.md",
-    "pages/assets/Pasted image 20220523051608.png",
+    "pages/Network of Nodes.md",
-    "pages/assets/Pasted image 20220520215517.png",
+    "pages/Set of Protocols.md",
-    "pages/assets/Pasted image 20220523051208.png",
+    "pages/Recipes.md",
-    "pages/Start Here.md",
+    "pages/Project Logos.md",
-    "pages/Logos Program.md",
+    "pages/Data Model and Concurrency.md",
-    "pages/Instructions.md",
+    "pages/Staking and Multi-DAG.md",
-    "pages/Living Database.md",
+    "pages/Mempool and Subnetworks.md",
-    "pages/BBA.md"
+    "pages/Tokenomics.md"
   ]
 }

.trash/Social Applications.md

@@ -7,7 +7,7 @@ dateUpdated: @today
 
 ---
 
-# Topic:
+# Topic: Social Applications
 #### Related:
 `ELI5 goes here`
 

Templates/2. Short Topic Template.md

@@ -0,0 +1,73 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

Templates/3. Long Topic Template.md

@@ -3,7 +3,6 @@ title:
 author:
 dateCreated: {{date:YYYYMMDD}}
 dateUpdated: @today
-
 ---
 
 # Topic: [Insert name] 
@@ -34,44 +33,3 @@ ELI5: Easy explainer for beginner.
  
 #### Knowledge Share:
 [Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
-
-
-
-*(Copy starting at the three hyphens below for a blank section template to use explain a new Topic)*  
-
----
-
-title:
-author:
-dateCreated: @today
-dateUpdated: @today
-
----
-
-# Topic:
-#### Related:
-`ELI5 goes here`
-
----
-
-## Overview
-
-#### Operating Definition:
-[Definition here]<sup>1</sup>
-
-#### Current "Standard" Implementation:
-
-
-#### The Idea(l):
-
-
-#### Logos Implementation:
-
-
-#### Live Feedback:
-
-
-#### IMPORTANT Differentiators:
-
-
-#### Knowledge Share:

pages/BBA.md

@@ -1,16 +1,20 @@
 ---
-
 title: 
 author:
-dateCreated: @today
+dateCreated: 
-dateUpdated: @today
+dateUpdated: 2022-05-23
+---
 
 ---
 
 # Topic: Binary Byzantine Agreement (BBA)
-#### Related: 
+## Chat: [Places for Live Discussion]
-`ELI5: Process of a distributed network coming to an agreement between two options OR the proposal, decision-making process, and eventual conclusion/convergence of a two-option Byzantine-contexted scenario. `
 
+#### Tags: [[Tags]] 
+
+```
+ELI5: Process of a distributed network coming to an agreement between two options OR the proposal, decision-making process, and eventual conclusion/convergence of a two-option Byzantine-contexted scenario.
+```
 ---
 
 ## Overview
@@ -18,19 +22,88 @@ dateUpdated: @today
 #### Operating Definition:
 Binary byzantine consensus concerns the problem of getting a set of distinct processes distributed across a network to agree on a single binary value 0 or 1 where processes can fail in arbitrary ways.<sup>1</sup>
 
-#### Current "Standard" Implementation:
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
 N/A
 
-#### The Idea(l):
+#### Implementation
+- Description and Explanation
 	N/A
-
+- Key Differences:
-#### Logos Implementation:
-Glacier
-
-#### Live Feedback:
-
-#### IMPORTANT Differentiators:
 	N/A
-
+- Additional Information:
-#### Knowledge Share:
 	N/A

pages/Consensus.md

@@ -1,6 +1,9 @@
-# Consensus
+---
+dateUpdated: 2022-05-24
+---
 
-### Related: 
+# Consensus
+A list of Topics necessary to develop better intuition and understanding
 
 - Recipe: [[BBA]]
 	- Prep: [||        ]
@@ -32,12 +35,12 @@
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1. 
+		1. https://www.geeksforgeeks.org/message-passing-model-of-process-communication/
 - Recipe: [[Gossip Protocol]] (is a subset of P2P Messaging)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1. https://en.wikipedia.org/wiki/Gossip_protocol#:~:text=A%20gossip%20protocol%20or%20epidemic,all%20members%20of%20a%20group.
+		1. https://en.wikipedia.org/wiki/Gossip_protocol#:~:text=A%20gossip%20protocol%20or%20epidemic,all%20members%20of%20a%20group
 - Recipe: [[Permissionless]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
@@ -108,148 +111,166 @@
 	- Cook Time: X min
 	- Ingredients:
 		1. https://medium.com/mechanism-labs/finality-in-blockchain-consensus-d1f83c120a9a5
-- Recipe: [[Social Applications]] (look up context)
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1.
 - Recipe: [[Bootstrapping]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1. https://en.wikipedia.org/wiki/Bootstrapping_node#:~:text=A%20bootstrapping%20node%2C%20also%20known,successfully%20join%20the%20overlay%20network.
+		1. https://en.wikipedia.org/wiki/Bootstrapping_node#:~:text=A%20bootstrapping%20node%2C%20also%20known,successfully%20join%20the%20overlay%20network
-- Recipe: [[Rounds]]
+- Recipe: [[Rounds]] (Communication)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://cseweb.ucsd.edu/~marzullo/pubs/harary.pdf
-- Recipe: [[Round-less]]
+		2. https://research.cs.cornell.edu/projects/Quicksilver/public_pdfs/2007PromiseAndLimitations.pdf
-	- Prep: [||||||||||]
+		3. https://en.wikipedia.org/wiki/Gossip_protocol
-	- Cook Time: X min
-	- Ingredients:
-		1.
 - Recipe: [[Paxos]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://lamport.azurewebsites.net/pubs/paxos-simple.pdf
 - Recipe: [[DAG-Based Consensus]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. https://www.sciencedirect.com/science/article/pii/S2352864819301476
-- Recipe: [[Liveness]]
+- Recipe: [[Safety vs Liveness]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://dl.acm.org/doi/pdf/10.1145/42282.42283 (Partial Synchrony)
+		2. https://www.scs.stanford.edu/~dm/blog/safety-vs-liveness.html
+		3. https://medium.com/codechain/safety-and-liveness-blockchain-in-the-point-of-view-of-flp-impossibility-182e33927ce6
+		4. https://en.wikipedia.org/wiki/Thread_safety
+		5. https://blog.blockstack.org/blockchains-and-consensus-protocols-liveness-and-correctness-are-inseparable/
 - Recipe: [[Asynchronous (P2P)]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. http://infolab.stanford.edu/~burback/dadl/node93.html#:~:text=In%20a%20distributed%20system%2C%20communication,others%20have%20slower%20clock%20cycles.
+		2. https://arxiv.org/pdf/2102.06804.pdf
+		3. https://dl.acm.org/doi/10.1145/3149.214121
 - Recipe: [[Execution-Layer Decoupling]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://subscription.packtpub.com/book/data/9781789804164/1/ch01lvl1sec07/layered-structure-of-the-blockchain-architecture#:~:text=For%20these%20applications%2C%20blockchain%20network,and%20rules%20that%20are%20executed
+		2. https://cointelegraph.com/blockchain-for-beginners/a-beginners-guide-to-understanding-the-layers-of-blockchain-technology
+		3. https://www.techopedia.com/definition/16907/decoupled-architecture
 - Recipe: [[Interchangeability]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://arxiv.org/pdf/2005.14282.pdf
-- Recipe: [[Liveness]]
+- Recipe: [[Distributed Systems]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients: 
-		1.
+		1. https://link.springer.com/article/10.1007/s00607-016-0508-7
+- Recipe: [[Safety vs Liveness]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients:
+		1. https://dl.acm.org/doi/10.1145/3149.214121
+		2. https://www.doc.ic.ac.uk/~jnm/book/firstbook/pdf/ch7.pdf
 - Recipe: [[Extensibility]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://www.semanticscholar.org/paper/An-Extensible-Consensus-Algorithm-Based-on-PBFT-Li-Wang/8b07a6c6efa551ac6531bf2f79c9010d53fff742
+		2. https://arxiv.org/pdf/2008.09518.pdf
+		3. https://www.frontiersin.org/articles/10.3389/fbloc.2020.00028/full
 - Recipe: [[Highly-Partitioned Blockchains with Local Views]] 
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://arxiv.org/pdf/1804.07356.pdf
+		2. https://www.comp.nus.edu.sg/~hobor/Publications/2021/OverlayChain.pdf
+		3. https://etd.ohiolink.edu/apexprod/rws_etd/send_file/send?accession=ksuhonors1588372348886683&disposition=inline
 - Recipe: [[Ordering]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://courses.grainger.illinois.edu/ece598pv/sp2021/lectureslides2021/ECE_598_PV_course_notes13.pdf
 - Recipe: [[Reputation]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://robertgreenfieldiv.medium.com/reputation-on-the-blockchain-624947b36897
 - Recipe: [[Confidence]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.258.9605&rep=rep1&type=pdf
+		2. https://www.robgjansen.com/publications/fet-csci5271.pdf
+		3. https://rtg.cis.upenn.edu/qtm/doc/p2p_reputation.pdf
 - Recipe: [[Network Congestion]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://en.wikipedia.org/wiki/Network_congestion
+		2. https://en.wikipedia.org/wiki/Network_scheduler
 - Recipe: [[Topology]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://dl.acm.org/doi/fullHtml/10.1145/3441692
 - Recipe: [[Resilience (Consensus context)]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://dl.acm.org/doi/abs/10.1145/800221.806706
-- Recipe: [[Verifiability]]
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1.
 - Recipe: [[Non-Repudiation]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://www.cryptomathic.com/products/authentication-signing/digital-signatures-faqs/what-is-non-repudiation
+		2. https://jwcn-eurasipjournals.springeropen.com/articles/10.1186/s13638-020-01665-w#:~:text=In%20blockchain%2C%20the%20non%2Drepudiation,information%20receiver%20cannot%20be%20denied.
 - Recipe: [[Snowball]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://assets.website-files.com/5d80307810123f5ffbb34d6e/6009805681b416f34dcae012_Avalanche%20Consensus%20Whitepaper.pdf
 - Recipe: [[Lachesis]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://arxiv.org/abs/2108.01900
+		2. https://fantom.foundation/blog/a-brief-intro-to-lachesis-consensus-engine/
+		3. https://www.fantom.foundation/lachesis-consensus-algorithm/
 - Recipe: [[Glacier]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://www.notion.so/Consensus-cca3f5b9bed341219d1cfd027bea897c#3bd35a9a31624bec95d711141cacb77b
 - Recipe: [[PoW]] (Proof of Work)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://en.wikipedia.org/wiki/Proof_of_work
 - Recipe: [[PoS]] (Proof of Stake)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/
 - Recipe: [[Classical Consensus]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://dzone.com/articles/evolution-of-consensus-mechanisms-from-classical-m
+		2. https://docs.thundercore.com/consensus-protocols-101.pdf
 - Recipe: [[Nakamoto Consensus]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://eprint.iacr.org/2019/943.pdf
+		2. https://docs.thundercore.com/consensus-protocols-101.pdf
 - Recipe: [[DAG-Based Consensus]] (Avalanche-Like)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
-		1.
+		1. https://arxiv.org/pdf/2012.06128.pdf
+		2. https://www.sciencedirect.com/science/article/pii/S2352864819301476
+		3. https://assets.ctfassets.net/r1dr6vzfxhev/2t4uxvsIqk0EUau6g2sw0g/45eae33637ca92f85dd9f4a3a218e1ec/iota1_4_3.pdf
+		4. https://domschiener.gitbooks.io/iota-guide/content/chapter1/current-role-of-the-coordinator.html
+		5. https://tokens-economy.gitbook.io/consensus/chain-based-dag/direct-acyclic-graph-tangle-dag#:~:text=Tangle%20is%20the%20DAG%20consensus,are%20added%20to%20the%20Tangle.
+		6. https://docs.thundercore.com/consensus-protocols-101.pdf

pages/DAG Bootstrapping.md

@@ -0,0 +1,73 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

pages/DAG Communication.md

@@ -0,0 +1,64 @@
+---
+dateUpdated: 2022-05-24
+---
+
+# DAG Communication
+A list of Topics necessary to develop better intuition and understanding
+
+- Recipe: [[Factory of DAGs]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients:
+		1. 
+	- Concept
+	- Algorithm
+- Recipe: [[Sub-DAG]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients:
+		1. 
+- Recipe: [[Cross-DAG]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Application-Level User-Driven]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Direct Communication Channel]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Direct Communication VGER]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: Topic
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: Topic
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: Topic
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: Topic
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]

pages/Data Model and Concurrency.md

@@ -1,6 +1,9 @@
-# Data Model and Concurrency
+---
+dateUpdated: 2022-05-24
+---
 
-### Related:
+# Data Model and Concurrency
+A list of Topics necessary to develop better intuition and understanding
 
 - Reference Work
 	- [[eUTXO]] (Direct extension of the basic UTXO model)

pages/Decentralized Storage.md

@@ -0,0 +1,2 @@
+# Decentralized Storage
+A list of Topics necessary to develop better intuition and understanding

pages/Dispersal.md

@@ -0,0 +1,2 @@
+# Dispersal
+A list of Topics necessary to develop better intuition and understanding

pages/Distributed Systems.md

@@ -0,0 +1,73 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

pages/Incentives.md

@@ -0,0 +1,2 @@
+# Incentives
+A list of Topics necessary to develop better intuition and understanding

pages/Leaderless.md

@@ -3,8 +3,8 @@
 
 title:
 author: 
-dateCreated: @today
+dateCreated: 
-dateUpdated: @today
+dateUpdated: 2022-05-23
 
 ---
 

pages/Liveness.md

@@ -1,36 +0,0 @@
----
-
-title:
-author: 
-dateCreated: @today
-dateUpdated: @today
-
----
-
-# Topic:
-#### Related:
-`ELI5 goes here`
-
----
-
-## Overview
-
-#### Operating Definition:
-[Definition here]<sup>1</sup>
-
-#### Current "Standard" Implementation:
-
-
-#### The Idea(l):
-
-
-#### Logos Implementation:
-
-
-#### Live Feedback:
-
-
-#### IMPORTANT Differentiators:
-
-
-#### Knowledge Share:

pages/Living Database.md

@@ -1,5 +1,7 @@
 # Living Database
+a description of what this can mean is found below
 
-Building a “living database” for human-machine intelligence analysis
 
-https://c4i.gmu.edu/~pcosta/F15/data/fileserver/file/472065/filename/Paper_1570111241.pdf
+https://c4i.gmu.edu/~pcosta/F15/data/fileserver/file/472065/filename/Paper_1570111241.pdf - Building a “living database” for human-machine intelligence analysis
+
+https://en.wikipedia.org/wiki/Controlled_natural_language

pages/Logos Program.md

@@ -1,8 +1,8 @@
 ---
 title: Logos Program
 author: 
-dateCreated: @today
+dateCreated: 2022-05-07
-dateUpdated: @today 2022-05-07
+dateUpdated: 2022-05-23
 ---
 
 # Logos Program
@@ -28,8 +28,8 @@ to [[Add New Topic]] or [[Edit an Existing Topic]] in the notebook
 ## Project Directory
 is a list of Projects involved in the Logos Program
 
-### [[Project Logos]]
 ### [[Project Codex]]
+### [[Project Logos]]
 ### [[Project Waku]]
 
 ---

pages/Low Node Count Consensus.md

@@ -0,0 +1,73 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

pages/Mempool and Subnetworks.md

@@ -0,0 +1,27 @@
+---
+dateUpdated: 2022-05-24
+---
+
+# Mempool and Subnetworks
+A list of Topics necessary to develop better intuition and understanding
+
+- Recipe: [[Censorship-Resistant]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Mempool Construction]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Traditional Sharding]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]
+- Recipe: [[Subnetwork Assignation Algorithm]]
+	- Prep: [||||||||||]
+	- Cook Time: X min
+	- Ingredients: 
+		1. [Insert pictures, videos, article links, research papers, etc.]

pages/Network Layer.md

@@ -1,20 +1,15 @@
-# Network Layer and Mempool
+---
+dateUpdated: 2022-05-24
+---
 
-### Related: 
+# Network Layer
+A list of Topics necessary to develop better intuition and understanding
 
 - [[Node Discovery]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[Subnetworks]]
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
-	- Design
-	- Implementation
-	- Ideas
 - [[Mempool]]
 	- Prep: [||||||||||]
 	- Cook Time: X min

pages/Network of Nodes.md

@@ -1,3 +1,7 @@
+---
+dateUpdated: 2022-05-24
+---
+
 # Network of Nodes
 
 ## The Waku Network  

pages/New SubDAG Creation.md

@@ -0,0 +1,73 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: [Insert Topic] 
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
+
+---
+
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
+
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic:  
+## Chat: 
+
+#### Tags: 
+
+```
+ELI5: Simple explainer.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

pages/Node Reputation.md

@@ -1,6 +1,9 @@
-# Node Reputation
+---
+dateUpdated: 2022-05-24
+---
 
-### Related: 
+# Node Reputation
+A list of Topics necessary to develop better intuition and understanding
 
 - [[Ikingut (Reputation Algorithm)]]
 	- Prep: [||||||||||]

pages/Principles.md

@@ -0,0 +1,32 @@
+# Our Principles
+
+I. Liberty
+We believe in the sovereignty of individuals. As a platform that stands for the cause of personal liberty, we aim to maximize social, political, and economic freedoms. This includes being coercion-resistant.
+
+II. Censorship resistance
+We enable free flow of information. No content is under surveillance. We abide by the cryptoeconomic design principle of censorship resistance. Even stronger, Status is an agnostic platform for information.
+
+III. Security
+We don't compromise on security when building features. We use state-of-the-art technologies, and research new security methods and technologies to make strong security guarantees.
+
+IV. Privacy
+Privacy is the power to selectively reveal oneself to the world. For us, it's essential to protect privacy in both communications and transactions, as well as being a pseudo-anonymous platform. Additionally, we strive to provide the right of total anonymity.
+
+V. Transparency
+We strive for complete openness and symmetry of information within the organization, and have no border between our core contributors and our community. We are frank about our shortcomings, especially when making short-term tradeoffs in service of our long-term goals.
+
+VI. Openness
+The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation.
+
+VII. Decentralization
+We minimize centralization across both the software and the organization itself. In other words, we maximize the number of physical computers composing the network, and maximize the number of individuals who have control over the system(s) we are building.
+
+VIII. Inclusivity
+We believe in fair and widespread access to our software, with an emphasis on ease-of-use. This also extends to social inclusivity, permissionless participation, interoperability, and investing in educational efforts.
+
+IX. Continuance
+We create software incentivized to continue to exist and improve, without the stewardship of a single entity or any of the current team members.
+
+X. Resourcefulness
+We are relentlessly resourceful. As we grow and have ready access to capital, it is our obligation to token holders to fight bureaucracy and inefficiencies within the organization. This means solving problems in the most effective way possible at lower economic costs (in terms of capital, time and resources).
+

pages/Project Codex.md

@@ -1,8 +1,8 @@
 ---
 title: Understanding Codex Efforts
 author: 
-dateCreated: @today
+dateCreated: 2022-05-07
-dateUpdated: @today 2022-05-07
+dateUpdated: 2022-05-23
 ---
 
 # Understanding Codex Efforts
@@ -18,16 +18,20 @@ Dmitriy Ryajov
 
 ## Necessary Terminology
 
-### Decentralized Storage
+### The Six (6) Technology Layers of Codex as a [insert here | Decentralized Storage Solution?]
-### Durability
-### Redundancy
-### Dispersal (FT or )
-### Incentives
-### Remote Auditing
 
-FT -> 
+#### 1. [[Decentralized Storage]]
+#### 2. [[Durability]]
+#### 3. [[Redundancy]]
+#### 4. [[Dispersal]]
+#### 5. [[Incentives]]
+#### 6. [[Remote Auditing]]
+
+Comments (Leo's comments re: organization of High-Level Categories)
+FT -> ???
 BFT -> Incentives + Remote Auditing
 
+### Unsorted Pages:
 [[storage]]
 [[data]]
 [[durability]] 

pages/Project Logos.md

@@ -1,8 +1,8 @@
 ---
 title: Understanding the Logos Blockchain Whitepaper | A High-Level Conceptual Review of the Logos Blockchain
 author: 
-dateCreated: @today
+dateCreated: 2022-05-07
-dateUpdated: @today 2022-05-07
+dateUpdated: 2022-05-24
 ---
 
 # Understanding the Logos Blockchain Whitepaper
@@ -15,11 +15,14 @@ This document reflects an approach of whitepaper review that combines a rough-dr
 
 ## Necessary Terminology by Layer
 
-### The Six (6) Technology Layers of Logos as a Blockchain
+### The Nine (9) High-Level Categories of Logos as a Blockchain
 
 #### 1. [[Consensus]]
 #### 2. [[Node Reputation]]
-#### 3. [[Network Layer and Mempool]]
+#### 3. [[Network Layer]]
-#### 4. [[Staking and Multi-DAG]]
+#### 4. [[Mempool and Subnetworks]]
-#### 5. [[Data Model and Concurrency]]
+#### 5. [[Staking and Multi-DAG]]
-#### 6. [[Tokenomics]]
+#### 6. [[Data Model and Concurrency]]
+#### 7. [[DAG Communication]]
+#### 8. [[Bootstrapping or Factory]]
+#### 9. [[Tokenomics]]

pages/Project Waku.md

@@ -17,7 +17,7 @@ dateUpdated: @today 2022-05-07
 
 ## Necessary Terminology by Perspective
 
-### The Three (3) Perspectives of Waku v2
+### The Three (3) High-Level Categories of Waku (v2)
 
 #### 1. [[Set of Protocols]]
 #### 2. [[Network of Nodes]]
@@ -40,7 +40,7 @@ ___
 [[privacy]]
 [[messaging]]
 [[secure-messaging]]
-[[censorship-resistant]]
+[[Censorship-Resistant]]
 [[regulation]]
 [[credible-neutrality]]
 [[adoption]]

pages/Recipes.md

@@ -6,8 +6,8 @@ basically a Topic with a cooking theme
  a new `Recipe Template` AND/OR a new `Topic Template`
  
 You can:
-1) Use command Ctrl+T or Cmd+T to insert a new [[Recipe Template]] (as seen below) for a new Topic. 
+1) Use command Ctrl+T or Cmd+T to insert a new [[1. Recipe Template]] (as seen below) for a new Topic. 
-2) Then you can use command Ctrl+T or Cmd+T again to populate the details of the new topic with the [[Topic Template]].
+2) Then you can use command Ctrl+T or Cmd+T again to populate the details of the new topic with the [[3. Long Topic Template]].
 
 ```
 - Recipe: Topic

pages/Redundancy.md

@@ -0,0 +1,2 @@
+# Redundancy
+A list of Topics necessary to develop better intuition and understanding

pages/Remote Auditing.md

@@ -0,0 +1,2 @@
+# Remote Auditing
+A list of Topics necessary to develop better intuition and understanding

pages/Rounds.md

@@ -1,16 +1,20 @@
 ---
-
 title: 
 author:
-dateCreated: @today
+dateCreated: 5-07-2022
 dateUpdated: @today
+---
 
 ---
 
-# Topic:
+# Topic: Rounds
-#### Related:
+## Chat: [Live Discussion]
-`ELI5 goes here`
 
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: PBFT variants have this concept of "rounds" which is all-to-all communication. We'd prefer to have "round-less" communication where nodes do not have to talk to all other nodes on a given network for scalability reasons.`
+```
 ---
 
 ## Overview
@@ -18,19 +22,52 @@ dateUpdated: @today
 #### Operating Definition:
 [Definition here]<sup>1</sup>
 
-#### Current "Standard" Implementation:
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
 
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]
 
-#### The Idea(l):
+---
 
+FILL IN ABOVE TEMPLATE AND DELETE BELOW -OR- COPY PASTA BELOW AND DELETE ABOVE
 
-#### Logos Implementation:
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
 
+---
 
-#### Live Feedback:
+# Topic:  
+## Chat: 
 
+#### Tags: 
 
-#### IMPORTANT Differentiators:
+```
+ELI5: Simple explainer.
+```
+---
 
+## Overview
 
-#### Knowledge Share:
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+N/A
+
+#### Implementation
+- Description and Explanation
+	N/A
+- Key Differences:
+	N/A
+- Additional Information:
+	N/A

pages/Safety vs Liveness.md

@@ -0,0 +1,40 @@
+---
+title: 
+author:
+dateCreated: 
+dateUpdated: @today
+---
+
+---
+
+# Topic: Safety vs Liveness
+## Chat: [Live Discussion]
+
+#### Tags: [Relevant Tags to Topic/Concept] see [[Tags]]
+
+```
+ELI5: 
+
+Consensus protocols provide two guarantees with respect to order and timing:
+
+Safety: As long as the protocol does not have more than some threshold of faulty participants, other participants cannot convince a client to accept an incorrect or invalid message.
+
+Liveness: So long as there is always at least one transaction suitable for inclusion that has not been deemed final by any properly-operating nodes, the set of transactions deemed final by at least one properly-operating node will increase in number. | As long as the protocol does not have more than some threshold of faulty participants, other participants cannot indefinitely delay the acceptance of a correct message.
+```
+---
+
+## Overview
+
+#### Operating Definition:
+[Definition here]<sup>1</sup>
+
+#### Principles
+[What principle(s) are we trying to protect by innovating on this front? The solution that is aligned with the original Ethereum ethos to which Status is preserving ideological alignment with.] see [[Principles]]
+
+#### Implementation
+- Description and Explanation
+	[Technical Why goes here. Systems that are very similar to us or are the current "best-in-class" that we are trying to improve upon for a given factor (define context-relevant network assumptions per phrase, ideally we'll come up with visual sliding bars to show complex relationships between increasing/decreasing factors and how we go from "research" assumptions to "production" engineering) and why?]  
+- Key Differences:
+	[Easy low-hanging fruit for marketing or communication that makes our implementation clearly different/better.]
+- Additional Information:
+	[Quickly share unread but potentially valuable resources and comments here to be re-read by someone else who can integrate them.]

pages/Set of Implementations.md

@@ -1,3 +1,7 @@
+---
+dateUpdated: 2022-05-24
+---
+
 # Set of Implementations
 
 ## Waku v2 builds on `libp2p`,  
@@ -13,26 +17,6 @@ For example, there are some [fundamental issues with encryption](https://github
 `libp2p` was developed for IPFS but now many projects use it, Ethereum 2 included. It is therefore quite mature, with many implementations and a large part of the crypto/p2p community behind it. While it’s not perfect, it’s very modular and easy to extend with new transports, user-defined protocols, etc.
 ```
 
-## **How-To (Get Cookin')**
-*Instructions: There are some descriptions below which detail the usage of visual guidance metrics available in the form of "cookbook-like" instructions for how to consume this document:*
-
-|  Gauges  |     Description    | Visualization |
-| -------- | :-----------: |  :----------:  |
-|Difficulty| 1-10 (Ticks/Pips) |  [||||||||||]  | 
-|Time      | In Minutes | X Minutes |
-|Resources | Article/Video Links w/ Visual Content | Conceptual & Pictoral "Ingredients List" of Links|
-
-### **Gauge Definitions:**
-
-Prep (*Difficulty*) is defined as the ease of which the concepts can be generally understood. (Future: Make into more fun visual or something more enjoyable than a difficulty bar.)
-
-Cook Time (*Scope*) is in reference to the size of information necessary to learn to gain a decent level of comprehension.
-
-Ingredients (*Resources*) is for links relevant to helping people understand the concepts. Number references and use superscript notation to reference mentions in terminology Recipes descriptions.
-
-
-	![[Pasted image 20220415164934.png]]
-
 - Recipe: [[nim-waku]]
 	- Prep: [||||||||||]
 	- Cook Time: X min

pages/Set of Protocols.md

@@ -1,3 +1,7 @@
+---
+dateUpdated: 2022-05-24
+---
+
 # Set of Protocols
 
 ## Waku v2 builds on `libp2p`,  

pages/Staking and Multi-DAG.md

@@ -1,88 +1,66 @@
+---
+dateUpdated: 2022-05-24
+---
+
 # Staking and Multi-DAG
+A list of Topics necessary to develop better intuition and understanding
 
-### Related: 
+- Recipe: [[Bridge (Intermediary) Nodes]]
-
-- [[Factory of DAGs]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-	- Concept
+- Recipe: [[Gravity]]
-	- Algorithm
-- [[Sub-DAG]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[Cross-DAG]]
+- Recipe: [[Application-Level User-Driven]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[Bridge (Intermediary) Nodes]]
+- Recipe: [[Direct Communication Channel]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[Gravity]]
+- Recipe: [[Direct Communication VGER]]
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
-- [[Application-Level User-Driven]]
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
-- [[Direct Communication Channel]]
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
-- [[Direct Communication VGER]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
 - Challenges
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
 	- [[Probabilistic finality]] and [[cross-network communication]]
 	- [[Network Partitioning]] and [[Forks]]
 	- [[Weak Subjectivity]] - Reputation of nodes matters to clients. Nodes are clients of other networks.
 	- [[Verifying Weights in Staking]]
 	- [[Glacier Algorithm Quiesces]]
-- [[Approach]]
+- Approach
-	- Prep: [||||||||||]
-	- Cook Time: X min
-	- Ingredients:
-		1. 
 	1. [[Deterministic Finality]]
 	2. [[Secondary Consensus Protocol]] (form local opinion on external DAG)
 	3. [[Intermediary DAG]] (Intersection of nodes participating mutually in common structures)
-- [[Vertex Sealing]]
+- Recipe: [[Vertex Sealing]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[XSub]] (Cross-sub-DAG communication)
+- Recipe: [[XSub]] (Cross-sub-DAG communication)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[XDAG]] (Cross-DAG communication)
+- Recipe: [[XDAG]] (Cross-DAG communication)
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[XDAG Fees]]
+- Recipe: [[XDAG Fees]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
 		1. 
-- [[Communication Patterns]]
+- Recipe: [[Communication Patterns]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:
@@ -90,7 +68,7 @@
 	- Direct
 	- User-Coordinated Channel
 	- Sub-DAG-Coordinated Channel
-- [[Stake Sub-DAG]]
+- Recipe: [[Stake Sub-DAG]]
 	- Prep: [||||||||||]
 	- Cook Time: X min
 	- Ingredients:

pages/Start Here.md

@@ -4,6 +4,6 @@ our Culinary Home where we create, prepare and cook World-Class Recipes
 
 [Under Construction: Insert 'Glad you finally made it' here video - VTuber Sprite of Chef]
 
-
-
 For now just hop into one of our Restaurants where our Chefs are busy at work: [[Logos Program]]
+
+Or you can skim the introduction here: [[Introduction]]

pages/Tokenomics.md

@@ -1,6 +1,9 @@
-# Tokenomics
+---
+dateUpdated: 2022-05-24
+---
 
-### Related: 
+# Tokenomics
+A list of Topics necessary to develop better intuition and understanding
 
 - [[Fees]]
 	- Prep: [||||||||||]

pages/Vac Program.md

@@ -62,7 +62,7 @@ ___
 [[privacy ]]
 [[messaging ]]
 [[secure-messaging ]]
-[[censorship-resistant ]]
+[[Censorship-Resistant ]]
 [[regulation ]]
 [[credible-neutrality ]]
 [[adoption ]]

pages/durability.md

@@ -1,36 +1,2 @@
----
+# Durability
-
+A list of Topics necessary to develop better intuition and understanding
-title:
-author:
-dateCreated: @today
-dateUpdated: @today
-
----
-
-# Topic: ?
-#### Related:
-`ELI5 goes here`
-
----
-
-## Overview
-
-#### Operating Definition:
-[Definition here]<sup>1</sup>
-
-#### Current "Standard" Implementation:
-
-
-#### The Idea(l):
-
-
-#### Logos Implementation:
-
-
-#### Live Feedback:
-
-
-#### IMPORTANT Differentiators:
-
-
-#### Knowledge Share: