From dd6231353e3f1aadd63b5c55a57d68596a87baf0 Mon Sep 17 00:00:00 2001 From: Daniel Sanchez Quiros Date: Thu, 1 Dec 2022 11:39:16 +0100 Subject: [PATCH] Added tiny node project information --- .../roadmap/consensus/development/prototypes.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/content/roadmap/consensus/development/prototypes.md b/content/roadmap/consensus/development/prototypes.md index 9533caf0d..aacdbac52 100644 --- a/content/roadmap/consensus/development/prototypes.md +++ b/content/roadmap/consensus/development/prototypes.md @@ -9,6 +9,20 @@ Consensus Prototypes is a collection of Rust implementations of the [Consensus C ## Tiny Node +Tiny node is a fake/basic implementation of the `Carnot` consensus protocol on top of a `Waku` network layer. + +The main idea is to have a node that can simulate the consensus protocol message passing through. So we can spawn testing networks +and measure the latencies of the necessary messages. + +We aim to have information enough to answer the question, do `Waku` works for the `Carnot` protocol? + +`Carnot` has a clear idea of how the network overlay should be. As a base overview, it is expected that the nodes are connected forming a **tree**. +We belive that this can be modeled with `Waku` in a logical way, but the underlaying `Waku` system will never be like that. +So we need to know if the pubsub system used by `Waku` will be enough for our purpoises. + + +There is currently an ongoing effort by Giacomo and Daniel centered in [the consensus branch](https://github.com/logos-co/nomos-research/pull/16) + ## Required Roles - Lead Developer (filled) \ No newline at end of file