Closed
Description
Crate
mostly relayer
and relayer-cli
, but may cross into modules
also
Problem Definition
Implement support for command:
relayer tx raw conn-try <to-chain-B> <remote-chain-A> <conn-id-on-A>
- sends request to local client for
chain-A
to retrieve latest headerheader_A
with heightha
- makes the following queries to
chain-A
at heightha-1
:
- the connection with idconn-id-on-A
with proof, stores results inconnection
andinit_proof
- the state of client with idconnection.client_id
and retrieves the height of last consensus state,last_cs_height
- the consensus state for client with idconnection.client_id
and heightlast_cs_height
with proof,consensus_proof
- sends a
MsgUpdateState
tochain-B
with:
client_id = connection.counterparty_client_id,
header = header_A,
signer = get_account(to-chain-B)
- sends a
MsgConnectionOpenTry
tochain-B
with
connection_id = connection.counterparty_connection_id,
client_id = connection.counterparty_client_id,
counterparty_connection_id = conn-id-on-A,
counterparty_client_id = connection.client_id,
counterparty_commitment_prefix = get_store_prefix(remote-chain-A),
counterparty_versions: connection.versions,
init_proof,
consensus_proof,
proofs_height = ha,
consensus_height = last_cs_height,
signer = get_account(to-chain-B)
Note: get_...
are functions that retrieve information from the relayer configuration.
For Admin Use
- Not duplicate issue
- Appropriate labels applied
- Appropriate milestone (priority) applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned