my test setup used two separate instances of provenance by modifying the remote
chain Makefile run-config
target with:
- $(BUILDDIR)/provenanced -t --home $(BUILDDIR)/run/provenanced init --chain-id=$(CHAIN_ID) testing2 --custom-denom=$(DENOM); \
don't commit Makefile
changes unless intended!!!
- i added the following to BOTH Makefile
run-config
targets. it creates consistent accounts for the relayer to use.
printf 'awesome eye lock unable enforce brand myth meadow flavor book energy borrow cloth field general enemy industry expose snow swim police vehicle naive neck' | build/provenanced -t --home build/run/provenanced keys add relayer --recover
build/provenanced -t --home build/run/provenanced add-genesis-account relayer 100000000000000nhash --keyring-backend test
- confirm ports, keys, etc in the relayer config. example included in this repo.
setup_local_chain.sh
andsetup_remote_chain.sh
(these configure and start the 2 chains)store_and_init_local_contract.sh
andstore_and_init_remote_contracts.sh
init_and_start_relayer.sh
for the relayer (takes several transactions to reach therunning
state)execute_contract.sh
performs a simple packet send from local -> remote with a final response back to local