New ADR 025 for passive channels

[michaelfig]

Description

This ADR is a proposal to enable "passive" IBC relayers (ones that manage a whole connection and detect when channels come and go), as well as an "attempt channel try open" callback to allow an application to decide how and whether to handle inbound channel open handshakes.

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

[clevinson]

@michaelfig Can you rename this to a nonconflicting ADR number (i think 025 is the lowest available). 023 is already in use here by this WIP ADR: #6083

[fedekunze]

Thanks @michaelfig. Concept ACK. It'd be great to have a bit more context by adding a few examples to ease the implementation process. 👍

[cwgoes]

Thanks, this is much clearer now, still a few questions on defaults and motivation.

[cwgoes]

ACK, but let's change to a default implementation instead of a alternative call path

[tac0turtle]

@Mergifyio refresh

[mergify]

Command refresh: success

[tac0turtle]

@michaelfig could you update to master or allow modifications

[michaelfig]

@michaelfig could you update to master or allow modifications

Updated to master. I don't know where to allow modifications, though.

[tac0turtle]

@Mergifyio refresh

[mergify]

Command refresh: success

[tac0turtle]

Updated to master. I don't know where to allow modifications, though.

seems like you need to update to master again. here is how you can allow modifications https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork and then we dont have to keep pinging you to update the pr

[michaelfig]

@Mergifyio refresh

FWIW, since I don't know if I'm allowed to tell the bot that. Guess I'm not.

seems like you need to update to master again.

Updated.

here is how you can allow modifications ... and then we dont have to keep pinging you to update the pr

I created this PR from an organization (agoric-labs) instead of my user account (michaelfig), so this option is not presented to me. Unfortunate, but apparently Github does not support that configuration... I guess they don't imagine orgs contributing to other orgs.

[mergify]

@michaelfig is not allowed to run commands