Mukan Erkin Törük
6852832fe8
1.4 KiB
| title | sidebar_label | sidebar_position | slug |
|---|---|---|---|
| Best Practices | Best Practices | 8 | /ibc/best-practices |
Best practices
Identifying legitimate channels
Identifying which channel to use can be difficult as it requires verifying information about the chains you want to connect to. Channels are based on a light client. A chain can be uniquely identified by its chain ID, validator set pairing. It is unsafe to rely only on the chain ID. Any user can create a client with any chain ID, but only the chain with correct validator set and chain ID can produce headers which would update that client.
Which channel to use is based on social consensus. The desired channel should have the following properties:
- based on a valid client (can only be updated by the chain it connects to)
- has sizable activity
- the underlying client is active
To verify if a client is valid. You will need to obtain a header from the chain you want to connect to. This can be done by running a full node for that chain or relying on a trusted rpc address. Then you should query the light client you want to verify and obtain its latest consensus state. All consensus state fields must match the header queried for at same height as the consensus state (root, timestamp, next validator set hash).
Explorers and wallets are highly encouraged to follow this practice. It is unsafe to algorithmically add new channels without following this process.