feat: Make Fruzhin configurable for different chains. #23
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
…ins via providing a chain name or a chain spec string.
Grigorov-Georgi
approved these changes
Sep 20, 2024
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.
Description
This PR allows Fruzhin web to connect to polkadot, kusama or westend chains via providing a chain name or a chain spec string as a parameter for the main method.
Enables configuration for chains different from polkadot.
To cover light client requirements.
The main method now requires a single parameter. It can be one of two:
1: Name of a well known chain (polkadot, kusama, westend).
2: A chain spec string of a well known chain.
Based on the provided a ChainService with the chain context is built and provided to the host to use.
Fixes LimeChain#531
Checklist: