Christopher Goes
Christopher Goes
> it cannot determine the state of the connection on destination chain B unless there is a query that looks up a connection with `{id: "conn_on_A", client_id: "clB_on_A"} in its...
> the chain accepts a Try message with empty connection id, picks the identifier and then validates the message Agreed - this is what I mean. The former is also...
Yes, this is a placeholder issue from a meeting. The basic idea is that it would be preferable to push the delay period choice out to the application level so...
cc @josef-widder @AdityaSripal @melekes
Per @AdityaSripal we can just add `NextValidatorsHash` to consensus states, so each consensus will have a height, a timestamp, a next validators hash, and an app hash. I suspect this...
> I am not sure about the consequences of removing validatorSet. Is the idea that once a header is verified we do not need to store the information anymore? Btw....
> > Yes; we can just store the hash of the validator set and/or next validator set, once verified. > > I guess we don't look into the validator set...
Ref https://github.com/cosmos/cosmos-sdk/issues/7176, small discrepancy in consensus state, should be easy to fix.
Alas I am a bit out of date on IBC standards - off the top of my head I'm not sure - @AdityaSripal might have a better idea.
This seems pretty straightforward to me. Any thoughts @AdityaSripal?