Make Fruzhin-web configurable for different well known chains. #531
Assignees
Milestone
Comments
6 tasks
Zurcusa
added a commit
to LimeChain/Fruzhin-Web
that referenced
this issue
Sep 24, 2024
# 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. - What does this PR do? Enables configuration for chains different from polkadot. - Why are these changes needed? To cover light client requirements. - How were these changes implemented and what do they affect? 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: - [X] I have read the [contributing guidelines](https://github.com/LimeChain/Fruzhin/blob/dev/CONTRIBUTING.md). - [X] My PR title matches the [Conventional Commits spec](https://www.conventionalcommits.org/). - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [X] All new and existing tests passed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue?
Motivation
A requirement for a light client is to connect to more than one chain.
Request
We need to make Fruzhin-web configurable for different well known chains. The following chains will be supported:
Solution
No response
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: