docs: IBC setup docs was added

docs/IBC-TRANSFER-WALKTHROUGH.md

@@ -0,0 +1,264 @@
+# IBC-transfer Walkthrough
+
+## Summary
+
+We will:
+1. Add relayer account in config.yaml file
+2. Specify the ports in config.yaml file
+3. Install the relayer
+4. Setup the relayer
+5. Start the chains
+6. Create the connection
+7. Create Channel
+8. Start the Relayer
+9. Make a Sample Transaction
+
+## Add relayer account in config.yaml file
+
+You need to add the relayer account in config.yaml file in both chains. To add relayer account, you can simply add the following lines in config.yaml.
+```
+- name: relayer
+  address : "<relayer_address>"
+  coins: ["10000000000upylon", "100000000ubedrock"]
+```
+`address` is template at this time, we need will update it later in the  guide.
+
+## Specify the ports in config.yaml file
+
+You need to specify the ports in `config.yaml` file so that both chains don't use the same port and also to avoid errors.
+The sample ports for `pylons/config.yaml` 
+  ```
+host:
+	  rpc: ":36659"
+	  p2p: ":36658"
+	  prof: ":6062"
+	  grpc: ":9991"
+	  api: ":1318"
+	  frontend: ":8081"
+	  dev-ui: ":12346"
+	  grpc-web: ":9093"
+```
+
+The sample ports for `juno/config.yaml` are: 
+```
+host:
+  rpc: ":26659"
+  p2p: ":26658"
+  prof: ":5062"
+  grpc: ":8991"
+  api: ":1316"
+  frontend: ":8081"
+  dev-ui: ":13346"
+  grpc-web: ":8093"
+```
+You can have different ports but the respective ports on both chain should not match.
+
+## Installing the relayer
+
+We will be using the @confio/ts-relayer.
+The Command to install the relayer is:
+`sudo npm i -g @confio/relayer@main`
+
+It will allows you to use following commands `ibc-setup` & `ibc-relayer`.
+
+Here is the Link for relayer installation : https://github.com/confio/ts-relayer
+
+## Setting-up the relayer
+
+First, you need to create a registry file. Command to create registry file is
+`ibc-setup init`
+This command will create a registry.yaml file.
+
+#### Configure Registry.yaml
+
+Open the file in VS code using the following command.
+`code ~/.ibc-setup/registry.yaml`
+Now, you need to add the chain's object and details of chains as follows.
+```
+chain:
+	juno:
+		chain_id: juno-1
+		prefix: juno
+		gas_price: 0.000001token
+		ics20_port: 'transfer'
+		rpc:
+		  - http://localhost:26659
+
+	pylons:
+		chain_id: pylons-1
+		prefix: pylo
+		gas_price: 0.000001ubedrock
+		ics20_port: 'transfer'
+		rpc:
+		  - http://localhost:36659
+```
+ ics20_port: if default = ‘transfer’ else you can found the port-id in `x/type/keys.go`.
+ rpc values can be found inside the `config.yaml` file in both chains.
+
+ ### Configure app.yaml
+
+ If app.yaml file is not already generated along side with the registry.yaml file. Use the following command to generate app.yaml file.
+ `ibc-setup init --src pylons --dest juno`
+ Open the app.yaml file in the editor using the following command.
+ `code ~/.ibc-setup/app.yaml`
+ The file will look like this.
+ ```
+src: pylons
+dest: juno
+mnemonic: stick deputy ankle near motion banana shift normal social hill between major
+srcConnection: connection-0
+destConnection: connection-0
+```
+Add `srcConnection: connection-0` & `destConnection: connection-0`
+The `mnemonic` will be used to generate the address of the relayer for both chains.
+
+### Get the relayer address for chain
+
+You will need to open terminal inside the chain's directory and run the following command.
+`<pylonsd> keys add relayer --recover --dry-run`
+Write the `mnemonic`  and press enter.
+The output will be like this.
+```
+abc@abc:~$ pylonsd keys add relayer --recover --dry-run
+> Enter your bip39 mnemonic
+stick deputy ankle near motion banana shift normal social hill between major
+
+- name: relayer
+  type: local
+  address: pylo1qvcf7rug8k0uumxdvy0mrkyug75s9umdfa9px9
+  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"Ak1JEnioXVLln60raRz8kRjhoykTaQR9Cl6pF/77+T5A"}'
+  mnemonic: ""
+
+
+```
+Copy the address and replace it in the `address` field in relayer account in the `<pylons>/config.yml`
+The lines below is for reference for updated `pylons/config.yaml`
+```
+accounts:
+  - name: alice
+    coins: ["20000000000upylon", "200000000ubedrock"]
+  - name: bob
+    coins: ["10000000000upylon", "100000000ubedrock"]
+  - name: relayer
+    address : "pylo1qvcf7rug8k0uumxdvy0mrkyug75s9umdfa9px9"
+    coins: ["10000000000upylon", "100000000ubedrock"]
+```
+ Repeat the same process for juno chain .
+
+ ## Start the chains
+
+ Start both chains by opening the terminal in the chain's directory and running the following commands.
+ ```
+starport chain init
+starport chain serve --force-reset
+
+```
+
+## Create the connection.
+
+After serving both chains, you will need to create a connection. This will take the details of the connection from the `registry.yaml` and `app.yaml` file.
+Command to create a connection is:
+`starport tools ibc-setup connect -- -v`
+
+The terminal output will be similar to this.
+```
+hassan@hassan-rns:~/work/src/old ones/pylons$ starport tools ibc-setup connect -- -v
+verbose: Queried unbonding period {"seconds":1814400}
+verbose: Create Tendermint client
+verbose: Queried unbonding period {"seconds":1814400}
+verbose: Create Tendermint client
+info: Connection open init: 07-tendermint-0 => 07-tendermint-0
+verbose: Get latest commit
+verbose: Get validator set for height 462
+verbose: Get header for height 462
+verbose: Get validator set for height 452
+verbose: Get header for height 452
+verbose: Update Tendermint client 07-tendermint-0
+info: Connection open try: 07-tendermint-0 => 07-tendermint-0 (connection-0)
+verbose: Get latest commit
+verbose: Get validator set for height 494
+verbose: Get header for height 494
+verbose: Get validator set for height 480
+verbose: Get header for height 480
+verbose: Update Tendermint client 07-tendermint-0
+info: Connection open ack: connection-0 => connection-0
+verbose: Get latest commit
+verbose: Get validator set for height 476
+verbose: Get header for height 476
+verbose: Get validator set for height 463
+verbose: Get header for height 463
+verbose: Update Tendermint client 07-tendermint-0
+info: Connection open confirm: connection-0
+Created connections connection-0 (07-tendermint-0) <=> connection-0 (07-tendermint-0)
+```
+
+## Create Channel
+
+To create the channel between the two chains, run the following command
+`starport tools ibc-setup channel -- --src-connection <connection-0> --dest-connection <connection-0> --src-port <transfer> --dest-port <transfer> --version ics20-1
+`
+
+`--src-connection` & `--dest-connection` are the fields you specified in `app.yaml` file.
+default `--src-port` is `transfer`
+default `--dest-port` is `transfer`
+
+Screenshot of the output:
+```
+hassan@hassan-rns:~/work/src/old ones/pylons$ starport tools ibc-setup channel -- --src-connection connection-0 --dest-connection connection-0 --src-port transfer --dest-port transfer --version ics20-1
+·
+· 🛸 Starport v0.19.5 is available!
+·
+· If you're looking to upgrade check out the instructions: https://docs.starport.network/guide/install.html#upgrading-your-starport-installation
+·
+··
+
+info: Create channel with sender pylons: transfer => transfer
+Created channel:
+  pylons-1: transfer/channel-0 (connection-0)
+  juno-1: transfer/channel-0 (connection-0)
+```
+
+## Start the Relayer
+
+The Command to start the relayer is:
+`starport tools ibc-relayer start -- -v`
+
+```
+hassan@hassan-rns:~/work/src/old ones/pylons$ starport tools ibc-relayer start -- -v
+·
+· 🛸 Starport v0.19.5 is available!
+·
+· If you're looking to upgrade check out the instructions: https://docs.starport.network/guide/install.html#upgrading-your-starport-installation
+·
+··
+
+info: Use last queried heights from /home/hassan/.ibc-setup/last-queried-heights.json file.
+verbose: [juno-1] Get header for height 632
+verbose: [pylons-1] Get header for height 614
+verbose: Get pending packets on pylons
+verbose: Get pending packets on juno
+info: Relay 0 packets from pylons => juno
+info: Relay 0 packets from juno => pylons
+verbose: Get pending acks on pylons
+verbose: Get pending acks on juno
+info: Relay 0 acks from pylons => juno
+info: Relay 0 acks from juno => pylons
+info: Timeout 0 packets sent from pylons
+info: Timeout 0 packets sent from juno
+verbose: next heights to relay {"packetHeightA":700,"packetHeightB":725,"ackHeightA":702,"ackHeightB":727}
+info: Ensuring clients are not stale
+verbose: Checking if juno has recent header of pylons
+verbose: Checking if pylons has recent header of juno
+info: Sleeping 60 seconds...
+
+```
+
+Relayer setup is completed now.
+
+ ## Sample Transaction
+
+ To do a transaction between the two chains, use the following command:
+
+ `<pylonsd> tx ibc-transfer transfer transfer channel-0 <reciever_address> 10000upylon --from <sender_address>`
+
+

docs/RECIPE_WALKTHROUGH.md

@@ -207,7 +207,7 @@ In the outputs field we return the new character by calling the item output ID.
 }
 ```
 
-This recipe should be even simplier to understand after building a base character. We fill the cookbook info, name, description, etc. with all the info the recipe needs to be identified. coinInputs and itemInputs remain empty because in this game, nothing is required to get LOUD coins. In itemOutputs however, we use a unique field for coin outputs ('coin'). Here we indicate what kind of coin it is through denom, and the amount we wish to output when this recipe is executed. No other field is required to fill in. Again, in outputs we call the item output ID with a weight of 1. In addition we've enabled the recipe.
+This recipe should be even simpler to understand after building a base character. We fill the cookbook info, name, description, etc. with all the info the recipe needs to be identified. coinInputs and itemInputs remain empty because in this game, nothing is required to get LOUD coins. In itemOutputs however, we use a unique field for coin outputs ('coin'). Here we indicate what kind of coin it is through denom, and the amount we wish to output when this recipe is executed. No other field is required to fill in. Again, in outputs we call the item output ID with a weight of 1. In addition we've enabled the recipe.
 
 ### Sword purchase recipe
 
@@ -486,9 +486,9 @@ Finally we have have our tradePercentage, tradeable, and outputs reflecting what
 }
 ```
 
-This recipe is complex, but given what we know from before let's dissect it. We have our identifiying information for the recipe in cookbookID, Id, name, etc. In order for the recipe to execute, we require a 'character' that requires XP at a minimum amount of 1, a level status at least at level 1, and it needs to have the entitiyType of a 'character'. We also need the sword that we created in the recipe earlier on, with the specific features we reference in the double/long/string fields. 
+This recipe is complex, but given what we know from before let's dissect it. We have our identifying information for the recipe in cookbookID, Id, name, etc. In order for the recipe to execute, we require a 'character' that requires XP at a minimum amount of 1, a level status at least at level 1, and it needs to have the entitiyType of a 'character'. We also need the sword that we created in the recipe earlier on, with the specific features we reference in the double/long/string fields. 
 
-Ouputs is where it gets interesting. First we output coins: if you look you can see we're giving back ten LOUD coins. In addition we have some unique items which look similar to the recipes we've toyed with before. We have a wolf tail and wolf fur (both have attacks at 0, level at 1, and value at 140). In ItemModifyOutputs, we can modify one of our inputs. In this case we modify our 'character' which we indicate with 'itemInputRef'. The modification looks the exact same as the other recipes we've built but we can use the program field to actively change our stats on chain. Note that we reference some of the past keys like level and XP. The program takes our previous stats and upgrades them within our program field.
+Outputs is where it gets interesting. First we output coins: if you look you can see we're giving back ten LOUD coins. In addition we have some unique items which look similar to the recipes we've toyed with before. We have a wolf tail and wolf fur (both have attacks at 0, level at 1, and value at 140). In ItemModifyOutputs, we can modify one of our inputs. In this case we modify our 'character' which we indicate with 'itemInputRef'. The modification looks the exact same as the other recipes we've built but we can use the program field to actively change our stats on chain. Note that we reference some of the past keys like level and XP. The program takes our previous stats and upgrades them within our program field.
 
 In our output field, we have five options for output. The output is determined by the weight: the higher the weight, the higher the chance of receiving that output. Within our entryIDs we reference which items we want to be outputted by calling the unique IDs.