Skip to content
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

Open
meetrick opened this issue Mar 8, 2024 · 7 comments
Open

Enabling Namada's IBC Transfer Support in Go-Relayer #2858

meetrick opened this issue Mar 8, 2024 · 7 comments

Comments

@meetrick
Copy link

meetrick commented Mar 8, 2024

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

  • Enable IBC transfer for the Namada protocol in Go-Relayer.
  • Currently, the DSRV team is compiling a list of patches made for the Namada protocol in the Hermes repository. We aim to integrate these patches into Go-Relayer. To achieve this, we believe mentorship from the Namada team would be beneficial.

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.

- shielded-expedition.88f17d1d14.json
{
  "type": "namada",
  "value": {
    "key": "default",
    "chain-id": "shielded-expedition.88f17d1d14",
    "rpc-addr": "http://localhost:26657",
    "account-prefix": "",
    "keyring-backend": "test",
    "gas-adjustment": 1.2,
    "gas-prices": "0.001naan",
    "debug": true,
    "timeout": "20s",
    "output-format": "json",
    "sign-mode": "direct"
  }
}
  • Could the Namada team provide advice on this matter? Sharing the experiences gained by the Namada team while writing the Hermes patch would likely be helpful.

@Fraccaman
Copy link
Member

@cwgoes

@meetrick
Copy link
Author

draft on cosmos/relayer

@cwgoes
Copy link
Contributor

cwgoes commented Mar 11, 2024

Do the Namada team have plans to support Go-Relayer?

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.

@meetrick
Copy link
Author

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.

@meetrick
Copy link
Author

meetrick commented Mar 18, 2024

@cwgoes We want to use the proto files of Namada so that go-relayer can support Namada.
To do this, we need to use the buf registry as follows. Could you help us write a buf registry for Namada?

@cwgoes
Copy link
Contributor

cwgoes commented Aug 27, 2024

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?

@meetrick
Copy link
Author

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.
Although it's already late to apply it to the testnet, I plan to proceed as a side project. Since Namada is also about to launch its mainnet soon, I definitely want to give it a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants