This is the script that needs to be run on both servers, except the chain id needs to be changed on the second server
now, alice wants to send some native token of chain test-2 to bob.
alice want to transfer some of her asset on chain test-2 to chain test-1.
alice want to delegate the rest of her tokens on chain test-2 to a validator on test-2.
setup:
channel-1
for ibc transfer.Now you can locally compile the binary and run commands from your computer that point to the two ip addresses of the two nodes:
show the setup
query ica acct
export ica acct
query the connection:
query the channel: you can see one channel for alice ica
ica register
cmd sends a new MsgChannelOpenInit
internally in the interchain accounts code here and emits the events which hermes listens to and detects, and then hermes finishes the channel handshake by sending the ChannelOpenTry to the counterparty chain (test-2).
faucet send some token to ica
bob now does not have any tokens
Step 1: generate the transaction json
step 2: send the generated tx json:
step1: create ibc channel (maybe ahead before demo)
step2:
step3: ibc tx by ica
query validator
val has 7000000000stake
val oper addr cosmosvaloper1hckrjqvuhdqncuuy73eu0engkgxn9gjds2jl5m
query ica delegation
when creating a new channel, when do tc by this new channel, hermes log: account sequence mismatch problem (this err only appear in hermes v0.9)
the fix was solved in v0.10, but v0.10 currently doesn't work with ICA
notes from Billy
test-2
via test-1
test-2
(AKA a')test-2