ibc-go
ibc-go copied to clipboard
cosmos
List which ICS corresponds to which IBC version
As IBC usage expands and chains in the wild might be using different versions, it would help knowing exactly which IBC version supports which ICS. Especially considering some ICS specs might get a v2 and so on. One use case would be the chain registry / CNS (as raised in cosmos/chain-registry#39 )
Most likely this data will be parsed automatically so a JSON file would be useful. Open to suggestions. I can understand there is a need to list this in the Readme as well. If so, perhaps a Github action could create a table from the JSON, for example.
As a rough idea I would propose something like the following:
"supported_ics": {
"1.2.1": [
"1",
"2",
// etc..
]
"2.1.0": [
"1",
"2",
"27",
//etc..
]
"3.2.0": [
"1",
"2v3",
"27v2",
//etc..
]
// etc
}
Excuse the random version numbers & ICSs, I'm not up to speed with the details.
@nooomski could you please move this issue to the ibc-go repository? I think it makes more sense to have this there, since its content will mention ibc-go versions.
Can't transfer, not admin, but would gladly remove and create a new one. @AdityaSripal are you able to transfer? Otherwise I'll remove & create new.
I think enabling in-protocol awareness of software versions and compatible IBC apps can be tremendously helpful for IBC, yes. Likely through some way of IBC querying, as well as RPC queries.
@nooomski how do you feel about this in the current environment? Also would like input from @AdityaSripal and @srdtrk on this.
Closing this for now. If there are any reasonable arguments to re-open, we can look into it.