Ethan Frey

Hi @silasdavis I think a good test harness that reproduces this case would be great place to start. I assume you have one from your comments? Would you be willing...

Yes, this is very close to what I had in mind (and what I sketched in an earlier IBC paper). Much more generic (given those golang structs are translated to...

I think this is a great idea, even if it seems like you are/were stuggling #164 and I am trying to document this as the default code review tool for...

Great, `cargo crev repo query review smallvec` gives all the info I wanted. This is an inspiring project. I should be commenting back after I've had time to use it...

@sunnya96 @valardragon this may be relevant to the token factory osmosis inplemented

One idea for backwards compatibility is to do this on a chain-by-chain basis. * v1 - v1 uses the current acknowledgement bytes both in the application interface and on the...

> Nice work, I think from a backwards compatibility standpoint. It is easier for the applications to still only create and process opaque bytes as the acknowledgement. > > Regardless...

I would deprecate this for the new ics-30 middleware solution being developed in #581 If that middleware solution is not followed, I would be happy to update this spec with...

Maybe. I think a discussion of actually providing structure to the acknowledgement would be a good thing. There is no concrete action item here

More metadata would be great. I think there is another issue somewhere tracking that, with some discussion