-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
15 changed files
with
427 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
storage/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
# Test ICQ wasm contract state using Juno testnet | ||
|
||
## 1. Install dependencies | ||
|
||
Read [instructions](https://docs.neutron.org/neutron/build-and-run/localnet) | ||
and install: | ||
- neutron | ||
- hermes | ||
- neutron query relayer | ||
|
||
## 2. Launch neutron | ||
|
||
Go to `neutron/` directory and run `make start`. | ||
This will deploy Neutron localnet. | ||
Please wait 20 to 30 seconds for chain to initialize before | ||
proceeding to step 3. | ||
|
||
## 3. Connect to Juno testnet | ||
|
||
Open `create_juno_connection.sh` in your text editor of choice. | ||
Navigate to `JUNO_MNEMONIC=""` and insert there your own testnet mnemonic. | ||
Please make sure to have at least 0.01 JUNOX on uni-6 testnet, these funds | ||
are needed to create a connection. | ||
|
||
Run `./create_juno_connection.sh`. After it finishes, `connection-0` should | ||
appear on Neutron localnet. You can use this snippet to query a list of | ||
connections on Neutron's localnet: | ||
|
||
```bash | ||
neutrond query ibc connection connections --node tcp://0.0.0.0:26657 --output json | jq '.connections[] | {id, client_id, state, counterparty}' | ||
``` | ||
|
||
If this is the first time you are running this script, you should only | ||
see `connection-0`. Don't worry if you see `connection-1`, `connection-2` | ||
and so on, simply use the last one you have created. | ||
|
||
## 4. Deploy ICQ relayer | ||
|
||
Open `icq.env` in your text editor of choice. | ||
Navigate to `RELAYER_NEUTRON_CHAIN_CONNECTION_ID=` and insert there | ||
connection ID you have just created. | ||
|
||
```bash | ||
rm -rf storage/; export $(xargs < icq.env) && neutron_query_relayer start | ||
``` | ||
|
||
## 5. Prepare to run test | ||
|
||
Open `test_wasm_query.sh` in your text editor of choice. | ||
Navigate to `CONNECTION_ID=""` and insert there | ||
connection ID you have just created. | ||
|
||
## 6. Run test | ||
|
||
Execute `./test_wasm_query.sh`. |
Oops, something went wrong.