Skip to content
This repository has been archived by the owner on Aug 2, 2024. It is now read-only.

feat: tendermint for substrate #896

Closed
AbdelStark opened this issue Jul 25, 2023 · 4 comments
Closed

feat: tendermint for substrate #896

AbdelStark opened this issue Jul 25, 2023 · 4 comments
Labels
consensus enhancement New feature or request stale

Comments

@AbdelStark
Copy link
Contributor

AbdelStark commented Jul 25, 2023

Implement Tendermint Consensus Compatible with Substrate

Description

The goal of this issue is to implement the Tendermint consensus algorithm in a way that is compatible with the Substrate framework. This will allow Madara to leverage the benefits of both the Tendermint consensus and the Substrate's modular framework.

Background

Tendermint is a Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine - written in any programming language - and securely replicates it on many machines. Substrate, on the other hand, is a modular framework that enables you to create purpose-built blockchains by composing custom or pre-built components.

Tasks

  1. Research: Understand the Tendermint consensus algorithm and how it can be integrated with the Substrate framework.
  2. Design: Create a design document detailing how the Tendermint consensus will be implemented in Madara. This should include any necessary changes to the existing architecture.
  3. Implementation: Implement the design, ensuring that the new consensus algorithm is fully compatible with Substrate.
  4. Testing: Write comprehensive tests to ensure the new consensus algorithm works as expected and does not introduce any regressions.
  5. Documentation: Update the project documentation to reflect the new consensus algorithm.

Acceptance Criteria

  • The Tendermint consensus algorithm is fully implemented and compatible with the Substrate framework.
  • The implementation passes all tests.
  • The project documentation is updated to reflect the new consensus algorithm.

Resources

@AbdelStark AbdelStark added enhancement New feature or request consensus labels Jul 25, 2023
@github-actions
Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

@github-actions github-actions bot added the stale label Aug 25, 2023
@adizere
Copy link

adizere commented Feb 5, 2024

Glad to help here! Our team is maintaining and actively developing CometBFT, the state of the art implementation of Tendermint consensus algorithm (used throughout the Cosmos ecosystem and beyond).

Note that the documentation linked in the original post to https://docs.tendermint.com/ is no longer maintained. Tendermint Core has been discontinued since December 2022. Reference. CometBFT is a fork and successor of Tendermint Core, so most projects switched to that.

@github-actions github-actions bot removed the stale label Feb 6, 2024
Copy link

github-actions bot commented Mar 8, 2024

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

@tdelabro
Copy link
Collaborator

tdelabro commented Aug 2, 2024

repository archived in favor of https://github.com/madara-alliance/madara

@tdelabro tdelabro closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
consensus enhancement New feature or request stale
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants