Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create list_of_IBC_channels.md (#345)
Closes: #XXX ## Context and purpose of the change There is no documentation about IBC channels. So people could open channels despite existing ones. or somebody could try to send IBC transaction via frozen channel. I've checked every single open channel from the Stride's side and write this table. It contain only latest data about existing IBC channels. If Stride <-> "foreign chain" have more then one open channel, I chose the one which is currently maintained and active. If client in channel probably frozen (bc of expired trusting period) this channel get label "frozen" ## Brief Changelog Add list_of_IBC_channels.md doc. ## Author's Checklist I have... - [ n/a] Run and PASSED locally all GAIA integration tests - [ n/a] If the change is contentful, I either: - [ n/a] Added a new unit test OR - [ n/a] Added test cases to existing unit tests - [ n/a] OR this change is a trivial rework / code cleanup without any test coverage If skipped any of the tests above, explain. No code added, only add useful documentation for IBC ## Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... - [ n/a] reviewed state machine logic - [ n/a] reviewed API design and naming - [ n/a] manually tested (if applicable) - [ n/a] confirmed the author wrote unit tests for new logic - [v] reviewed documentation exists and is accurate ## Documentation and Release Note - [ n/a] Does this pull request introduce a new feature or user-facing behavior changes? - [n/a ] Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? - [ n/a] This pull request updates existing proto field values (and require a backend and frontend migration)? - [ n/a] Does this pull request change existing proto field names (and require a frontend migration)? How is the feature or change documented? - [ n/a] not applicable - [ n/a] jira ticket `XXX` - [ n/a] specification (`x/<module>/spec/`) - [ v] README.md - [ n/a] not documented
- Loading branch information