RFC: Remove GrazChain #115
codingki
announced in
Announcements
Replies: 1 comment
-
in 0.1.x Commit: 5211161 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This RFC (Request for Comments) document outlines the breaking changes, updates, and new features planned for removing
GrazChain
type and usage.Motivation
Because we are going to release a new cli for chain info/data generation straight from source ex: https://github.com/cosmos/chain-registry called wadesta. I suggest a different approach filling custom value into graz.
Our initial intention having
GrazChain
is for adding and only using required value for interacting with clients and signingClients.Current
GrazChain
We adding
rpcHeaders
andgas
in there for interacting withclients
andsigningClient
for simplicity, but this can make a different problem when you already have aChainInfo
you will need to mutate those constants. this is not a good approach.Goals
in v0.1.x when you
connect
you will need just thechainId
,GrazChain
is not longer be the parameter inconnect
. We will removeGrazChain
and we will usingChainInfo
type from keplr so You will need to pass an array ofChainInfo
toGrazProvider
.example:
What if We want to add
rpcHeaders
andgas
?We will have a new params to the
grazOptions
calledchainsConfig
it's a record ofChainConfig
ChainsConfig
ChainConfig
so in
GrazProvider
will be like this:Conclusion
This RFC document has outlined the motivations, goals, and breaking changes planned for removing
GrazChain
type and usage.Feedback and suggestions from the graz community are highly appreciated. Please provide your input and comments on this RFC to help shape the future of graz and ensure that it meets the needs of the developers.
Beta Was this translation helpful? Give feedback.
All reactions