-
Notifications
You must be signed in to change notification settings - Fork 296
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
Tracking issue: MVP IBC Relayer infrastructure #465
Comments
Acceptance criteria: Relayer can execute a full chain of IBC actions, relayer code merged upstream & Strangelove responsible for maintenance |
Next step here is to use the go buf build process |
@avahowell Could you provide an update here about where things stand on the Relayer work? |
Good progress made this sprint, need sync'ing with SL tomorrow. |
Updating the current state of play:
Depending on which chain is "first" in the path, there will be different sequences of messages sent to each chain. I noticed that the failures were happening on the remote The current status is this output: `pd` log output
@avahowell suspects that changes to the ICS23 proof spec may be to blame, but I'm not sure I understand why (wouldn't those block earlier parts of the handshake?). |
The images pushed to `ghcr.io/penumbra-zone/penumbra` already include `pd` and `pcli`, but not `pclientd`. The latter will be necessary for integration in interchain test. Refs #465.
We debugged this today and are now at the point where the relayer can successfully handshake between two chains. The previous issue was that we had a logic bug in both the connection and channel handshakes introduced after some underlying tendermint-rs changes. The next step is to test the |
Towards #465. Here we define a container image that wraps the upstream cosmos/relayer image with the custom scripting for bootstrapping clients on the Penumbra testnet and preview networks. No other chain configs are part of this container image as of yet. The container image will be publicly available as `ghcr.io/penumbra-zone/relayer`. It isn't yet deployed to the cluster: that'll come next.
Towards #465. Here we define a container image that wraps the upstream cosmos/relayer image with the custom scripting for bootstrapping clients on the Penumbra testnet and preview networks. No other chain configs are part of this container image as of yet. The container image will be publicly available as `ghcr.io/penumbra-zone/relayer`. It isn't yet deployed to the cluster: that'll come next.
Towards #465. Here we define a container image that wraps the upstream cosmos/relayer image with the custom scripting for bootstrapping clients on the Penumbra testnet and preview networks. No other chain configs are part of this container image as of yet. The container image will be publicly available as `ghcr.io/penumbra-zone/relayer`. It isn't yet deployed to the cluster: that'll come next.
Adds a new "relayer" helm chart for deploying the custom relayer container image for penumbra preview <-> testnet paths. In the process, reorganizes the helm charts for ci into a subdir. Towards #465.
Adds a new "relayer" helm chart for deploying the custom relayer container image for penumbra preview <-> testnet paths. In the process, reorganizes the helm charts for ci into a subdir. Towards #465.
Adds a new "relayer" helm chart for deploying the custom relayer container image for penumbra preview <-> testnet paths. In the process, reorganizes the helm charts for ci into a subdir. Towards #465.
We now have a relayer deployment, updated on every merge into main. Its only path is between the preview and testnet environments, and that path is destroyed and rebuilt on every deploy. The logs on the service show a considerable number of warnings:
There's also a preponderance of errors of a specific type:
but the relayer docs say:
So that's to be expected. |
Overview
In order to relay IBC packets into Penumbra, we need a way to include the packets in transactions (#464), but we also need software that relayers can run to actually create those transactions.
What does this entail? TBD: let's figure this out (cc: @jackzampolin)
Next steps
ConnectionOpenAck
handling #2252The text was updated successfully, but these errors were encountered: