Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Baseline Tendermint implementation design #1837

Open
4 of 14 tasks
stranger80 opened this issue Apr 23, 2024 · 3 comments
Open
4 of 14 tasks

Baseline Tendermint implementation design #1837

stranger80 opened this issue Apr 23, 2024 · 3 comments
Assignees
Milestone

Comments

@stranger80
Copy link

stranger80 commented Apr 23, 2024

Objective

Create a design note and work breakdown structure for the baseline Tendermint implementation in Golang.

More details on notion

WIP: notes, design and implementation

Phase 0 - Start

  • Gather resources/Read paper - must read
  • Identify Edge cases.
  • Design tests
  • Feedback/Review

Phase 1 - POC

  • Implement algorithm.
  • Thoroughly Test algorithm.
  • Feedback/Review

Phase 2 - Extended POC

  • Setup simple generic data producing nodes
  • Test with setup on different configurations
  • Feedback/Review

Phase 3 - Tendermint Exp

  • Setup simple striped down juno nodes (partial integration with juno)
  • check for edge cases and integration issues
  • Test with setup on different configurations
  • Feedback/Review

Phase 4 - Integrate with juno

TBD ...

@obasekiosa
Copy link
Contributor

obasekiosa commented Apr 23, 2024

Work breakdown structure added in issue description.

@stranger80
Copy link
Author

@obasekiosa this link ("More details on notion") is broken - what's the latest version of this article?

@obasekiosa
Copy link
Contributor

@obasekiosa this link ("More details on notion") is broken - what's the latest version of this article?

Ahhh yes thanks!!
fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready For Release
Development

Successfully merging a pull request may close this issue.

3 participants