Add a step to get Nitro node's info

testnet-nitro-node.md

@@ -141,9 +141,11 @@ Nitro nodes can be run using Ansible either locally or on a remote machine; foll
 
 ### Check Deployment Status
 
-* Run the following command in the directory where the deployments are created:
+* Run the following commands on deployment machine:
 
   ```bash
+  DEPLOYMENTS_DIR=<path-to-deployments-dir>
+
   cd $DEPLOYMENTS_DIR/nitro-node
 
   # Check the logs, ensure that the nodes are running
@@ -156,14 +158,31 @@ Nitro nodes can be run using Ansible either locally or on a remote machine; foll
   # nitro-node-1  | 2:04PM INF Completed RPC server initialization url=127.0.0.1:4005/api/v1
   ```
 
+* Get your Nitro node's info:
+
+  ```bash
+  laconic-so deployment --dir l1-nitro-deployment exec nitro-rpc-client "nitro-rpc-client get-node-info -p 4005 -h nitro-node"
+
+  # Expected output:
+  # {
+  #   "SCAddress": "0xd0eA8b27591b1D070cCcD4D30b8D408fe794FDfc",
+  #   "MessageServicePeerId": "16Uiu2HAmSHRjoxveaPmJipzmdq69U8zme8BMnFjSBPferj1E5XAd"
+  # }
+
+  # SCAddress -> nitro address, MessageServicePeerId -> libp2p peer id
+  ```
+
 ## Create Channels
+
 Create a ledger channel with the bridge on L1 which is mirrored on L2
 
-* Run the following commands from the directory where the deployments are created
+* Run the following commands deployment machine:
 
 * Set required variables:
 
   ```bash
+  DEPLOYMENTS_DIR=<path-to-deployments-dir>
+
   cd $DEPLOYMENTS_DIR/nitro-node
 
   # Fetch the required Nitro node config