Ethan Frey

Trying to summarize again... * All fee escrow/payment logic is done in the source chain - this is implementation specific but does not need to be in the ibc spec...

If so, I see two potential ways to do this: 1. every ICS application spec will need to pass this field in their app-specific acknowledgement messages. This must be passed...

I think part of my reservation of (1) and placing the fee refunding logic into the ibc application comes from writing ibc-enabled CosmWasm contracts. Forcing each of them to properly...

> My two concerns are if there is any legal implications with paying fees based on packet type (especially the DEX example you posted above). The other is the relayer...

Thank you for your comments, Anka. I agree with most of this, but consider the go structs above a loose prototype, and I would propose different go implementations that also...

> chain B recv_packet handler stores the pay_to along with the ack bytes (when write ack happens) This is the key change and what affects the payloads and proofs between...

@kostko The supported hash functions are defined here: https://github.com/confio/ics23/blob/master/proofs.proto#L5-L13 The implementation to validate any proof in the ics23 format is also included in that repo. Note that the Cosmos IAVL...

> We are using SHA-512/256 which is the truncated version of SHA-512 with its own IVs so you cannot just use SHA-512 (which is supported in the above implementation under...

The rust implementation is inside confio/ics23. As is the Go and TypeScript. They are all kept in the same repo to ensure they stay in sync.

I'm curious. Can you expand a bit more? (I assume this is a personal placeholder issue). This is when you set/change the per-channel delay period and how that change can...