Implement ADR 25: IBC Passive Channels

[fedekunze]

Implement ADR 025 - IBC passive Channels

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[cwgoes]

@michaelfig Do you want to implement this, or should someone else take it on?

[michaelfig]

I'd love to see this implemented, and would be even happier if someone else did it! Would be willing to review PRs.

[cwgoes]

I'd love to see this implemented, and would be even happier if someone else did it! Would be willing to review PRs.

Do you still need it on Agoric's end? I think Agoric is probably best able to implement this since you have the clearest idea of the requirements for contract interactions (though it might be good to consult with CosmWASM as well).

[michaelfig]

Do you still need it on Agoric's end? I think Agoric is probably best able to implement this since you have the clearest idea of the requirements for contract interactions (though it might be good to consult with CosmWASM as well).

That's fine with me, I'm just not sure when we'll get the cycles to do this. It is not strictly necessary for us until we start having contracts that dynamically establish new IBC channels across existing IBC connections.

[ethanfrey]

This may be obsolete now. I managed to get all this functionality (passively watching all channels on a given connection) simply by adding a packetConnection attribute to sendpackets and acknowledgement events: cosmos/cosmos-sdk#8458

This is enough for our ts-relayer to auto-detect two channels (that's as far as we've gone in the CI tests)

[colin-axner]

Closing since I believe the desired features are already supported. Please let me know if I am incorrect in this assumption