You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a restart of the pods for whatever reason, it seems that the ibc client get expired fairly quickly.
Note: IBC client expiry is not limited to restarts of pods. So this needs to be solved more genrally as well.
Proposal
We should add a way to revie an IBC-client.
Initial thought is to have an /ibc/client-prop endpoint (we can have a better name), on the exposer itself. This can provide admin functions to submit a gov prop, pass it: for the ibc client
We can also just create an endpoint to be more specific to revive a
Alternatives
Work with timeouts, to have a more reasonable setting. Expose this to the config, so this is user defined and specific
Have traffic emulators running, that will keep performing txns on the chains to emulate ibc transations as well. This will make expriy of clients more rare.
The text was updated successfully, but these errors were encountered:
Overview
If there is a restart of the pods for whatever reason, it seems that the ibc client get expired fairly quickly.
Proposal
We should add a way to revie an IBC-client.
Initial thought is to have an
/ibc/client-prop
endpoint (we can have a better name), on the exposer itself. This can provide admin functions to submit a gov prop, pass it: for the ibc clientWe can also just create an endpoint to be more specific to revive a
Alternatives
The text was updated successfully, but these errors were encountered: