feat(consensus): alternate engine support - gordian #1265
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Reecepbcups
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
To support gordian, we need an easy interface we can plug another consensus client into. On start of an application, ICT figures out which you are using (cometbft or gordian), then uses the proper Consensus Client based on that finding. As a user no extra configuration is required to use gordian, just plug in the docker image.
Context
This builds off a similar approach used in cosmos/relayer#1490 for the relayer w/ CometBFT (Gordian: cosmos/relayer#1492)
This PR builds off other work here: #1205, and #1208.
TODO