Objective
Relayers need to use identifiers to specify clients, connections, channels and ports. Currently the identifiers are generated randomly. However, to aid the relayers they should be semi-structured.
The proposed changes are as follows:
- Client Identifiers should be prefixed with their client type for consistency with
ibc-go
- they should have a unique 8 character suffix matching
[0-9a-zA-Z]
- example:
08-wasm-Fj06bZ84
- Connection Identifiers should be prefixed with
connection
- they should have a unique 8 character suffix matching
[0-9a-zA-Z]
- example
connection-8bvC6762
- Channel Identifiers should be prefixed with
channel
- they should have a unique 8 character suffix matching
[0-9a-zA-Z]
- example
channel-972309bR
- Port Identifiers should be chosen depending on their purpose
Origin Document
https://hermes.informal.systems/tutorials/local-chains/add-a-new-relay-path.html#identifiers
Goals
- Update the identifier logic to follow the patterns above
- Update the unit tests
- Update any usages of the identifiers in the code to match the new pattern
Deliverable
Non-goals / Non-deliverables
- Change any logic where identifiers are being used outside of making them conform to the new standard
General issue deliverables
Testing Methodology
Creator: @h5law
Co-Owners: @h5law
Objective
Relayers need to use identifiers to specify clients, connections, channels and ports. Currently the identifiers are generated randomly. However, to aid the relayers they should be semi-structured.
The proposed changes are as follows:
ibc-go[0-9a-zA-Z]08-wasm-Fj06bZ84connection[0-9a-zA-Z]connection-8bvC6762channel[0-9a-zA-Z]channel-972309bRtransferOrigin Document
https://hermes.informal.systems/tutorials/local-chains/add-a-new-relay-path.html#identifiers
Goals
Deliverable
Non-goals / Non-deliverables
General issue deliverables
Testing Methodology
make ...make ...make test_allLocalNetis still functioning correctly by following the instructions at docs/development/README.mdk8s LocalNetis still functioning correctly by following the instructions hereCreator: @h5law
Co-Owners: @h5law