Enabling Namada's IBC Transfer Support in Go-Relayer

[meetrick]

Enabling Namada's IBC Transfer Support in Go-Relayer

• ref: https://github.com/heliaxdev/hermes/tree/v1.7.4-namada-beta7

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

• We have created an issue in the cosmos/relayer repository regarding the Namada protocol, and we are collaborating on it with mentoring from Strangelove.
  • Enabling Namada's IBC Transfer Support in Go-Relayer cosmos/relayer#1418

---

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]

@cwgoes

[meetrick]

draft on cosmos/relayer

• Namada support v2 cosmos/relayer#1419
  • We will gather the necessary information from the namada team and continue our work.

[cwgoes]

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]

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]

@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?

• https://buf.build/penumbra-zone/penumbra/docs/main

[cwgoes]

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]

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.