You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an umbrella ticket to capture references and discussion around knowledge transfer of the Consensus module. The primary focus is to onboard a new team member to co-own the module.
State sync is not implemented yet. The most basic version of it is in review in #812 and #874.
Note that this implementation uses the FSM (Finite State Machine) but we have decided to remove it as it is adding more complexity than simplicity to the codebase. We plan to make an ADR for this and likely remove it in #821.
The following is a screenshot from another thread (p2p related) we had just to show how hotstuff linear complexity works and how it relates to other types of gossip.
4. Goals
Get the consensus module to a TestNet ready stage
Leverage the perspective of someone new in order to update the tooling & documentation
Identify and resolve low-hanging fruit
Complete a few starter tasks and one major task
Determine the missing gaps and define a path forward for HotPOKT
Identify a co-owner and additional Point of Contact (POC) for the V1 Consensus module
Outline & document follow-up work & tasks to build & scale the Consensus module
@red-0ne Friendly reminder that if you're ever blocked on something or waiting on someone, this should capture the first 3 months of onboarding in terms of goals & deliverables.
Objective
This is an umbrella ticket to capture references and discussion around knowledge transfer of the Consensus module. The primary focus is to onboard a new team member to co-own the module.
1. Origin Document
2. Knowledge Transfer FAQ
We've got a basic version of 3-phase Hotstuff w/ deterministic round robin leader election driving the entire blockchain
State sync is not implemented yet. The most basic version of it is in review in #812 and #874.
Note that this implementation uses the FSM (Finite State Machine) but we have decided to remove it as it is adding more complexity than simplicity to the codebase. We plan to make an ADR for this and likely remove it in #821.
The libraries for VRF leader election are in place but have not been integrated into the rest of the codebase.
We use a basic round-robin approach right now.
We haven't implemented penalties double signing yet, or any mechanism related to "evidence" in Tendermint.
There's also a ton of opportunity for this like inactivity leaks and implementing other penalties since we're building our own L1 ;)
Our block & signature validation process. It's not documented well and there are not sufficient tests in place.
Points of contact for related ongoing work
@bryanchriswhite 🌐
@dylanlott 💾
@h5law 🌲
@okdas 🏗️
@adshmh 🚄
3. HotPOKT
The following is a screenshot from another thread (p2p related) we had just to show how hotstuff linear complexity works and how it relates to other types of gossip.
4. Goals
4.1 Starter Tasks
LocalNet
from scratch, the firstTriggerNextView
leads to height 2 and not 1 #4414.2 Required Deliverables
4.3 Stretch Deliverables
4.4 Non-Deliverables
4.5 Non-goals
Creator: @Olshansk
Co-Owners: @red-0ne
The text was updated successfully, but these errors were encountered: