Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Pseudocode for core-consensus protocol #176

Open
6 tasks
liamsi opened this issue Jun 1, 2021 · 0 comments
Open
6 tasks

Pseudocode for core-consensus protocol #176

liamsi opened this issue Jun 1, 2021 · 0 comments

Comments

@liamsi
Copy link
Member

liamsi commented Jun 1, 2021

Summary

We use tendermint but already incorporated some changes in the core protocol and plan to do more changes. IMO, it is required to have a high-level description of the consensus including a very simple abstraction of the ABCI boundary.

This work is a really example in my opinion:

Action Items

Open separate issues about these:

  • describe the current LL implementation consensus (basically including preprocess phase)
  • specify future required changes
    • changes to preprocess phase to include intermediate state roots
    • FinalizeBlock?
    • AFAIR, even the simple version of fee-burning required some changes to ABCI
    • later (after devnet): immediate execution
@liamsi liamsi added this to Sprint Pool in Weekly Sprint (core/app/libs) via automation Jun 1, 2021
@liamsi liamsi added this to To do in LazyLedger MVP via automation Jun 1, 2021
@liamsi liamsi changed the title Proposal: Pseudocode for core-consensus protocol Pseudocode for core-consensus protocol Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

1 participant