Closed ashuralyk closed 1 year ago
There's also a fix here: https://github.com/synapseweb3/forcerelay/pull/332/files#diff-bd738465789eac4c814d5379f1cbd380a8c8f9af159265b7b135fa3e23ed8002
The client type hash has already been retrieved, so it's not necessary to get client id from config again.
There's also a fix here: https://github.com/synapseweb3/forcerelay/pull/332/files#diff-bd738465789eac4c814d5379f1cbd380a8c8f9af159265b7b135fa3e23ed8002
The client type hash has already been retrieved, so it's not necessary to get client id from config again.
OK, got, I'll close it later
Description
while the generation of
client_id
in ckb4ibc monitor is assumed the counterparty is ckb4ibc itself, the test between ckb and axon will trigger an unwrap error because there is no ckb4ibc chain installed inconfig.toml
file, it's axon chain instead