-
Notifications
You must be signed in to change notification settings - Fork 951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling Namada's IBC Transfer Support in Go-Relayer #2858
Comments
draft on
|
Heliax does not plan to support the Go relayer internally. We'd be thrilled if you take on this effort, and happy to support you with any questions, concerns, requisite changes, etc. |
It seems like it will take a considerable amount of time, but we intend to proceed with it. We look forward to receiving various pieces of advice. |
@cwgoes We want to use the proto files of Namada so that go-relayer can support Namada. |
Hi, sorry for the slow response here. We have this but it's probably not that helpful to you. Are you still working on Go relayer support? |
Hey, Thanks response. |
Enabling Namada's IBC Transfer Support in Go-Relayer
Background
Exclusive Support by Hermes for the IBC Transfer in the Namada Protocol Poses a Significant Disruption Risk for Users and Developers in the Cosmos Ecosystem. Hence, It's Imperative for Go-Relayer to Extend Support for Namada.
Proposal
Do the Namada team have plans to support Go-Relayer? If so, I am interested in participating. If there are no plans, the DSRV team is eager to contribute.
Todo
question
Is the Namada protocol intending to maintain the memo size limit at 200 even after the mainnet launch? Or was the memo size limit adjusted specifically for shielded expedition purposes?
In order for go-relayer to support IBC transfers of the Namada protocol, it needs to be able to recognize Namada chain information. If we create the chain format as shown below, modifications and additions to the code related to type, memo, account-prefix, denom will be necessary.
The text was updated successfully, but these errors were encountered: