Merge pull request #1046 from kaleido-io/doc-upgrades

update public chain docs

Author: peterbroadhurst

docs/tutorials/chains/arbitrum.md

@@ -48,7 +48,7 @@ To create a local FireFly development stack and connect it to the Arbitrum testn
  - Connect to an ethereum network
  - Use the `evmconnect` blockchain connector
  - Use an remote RPC node. This will create a signer locally, so that our signing key never leaves the development machine.
- - Set the remote RPC node URL to `https://goerli-rollup.arbitrum.io/rpc` (for a full list of testnet RPC node urls visit https://developer.offchainlabs.com/docs/Public_Chains)
+ - See the Arbitrum [docs](https://developer.offchainlabs.com/node-running/node-providers) and select an HTTPS RPC endpoint.
  - Set the chain ID to `421613` (the correct ID for the Binance Smart Chain testnet)
  - Merge the custom config created above with the generated `evmconnect` config file
 
@@ -59,7 +59,7 @@ ff init arbitrum 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url https://goerli-rollup.arbitrum.io/rpc \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 421613 \
     --connector-config ~/Desktop/evmconnect.yml
 ```

docs/tutorials/chains/avalanche.md

@@ -48,7 +48,7 @@ To create a local FireFly development stack and connect it to the Avalanche Fuji
  - Connect to an ethereum network
  - Use the `evmconnect` blockchain connector
  - Use an remote RPC node. This will create a signer locally, so that our signing key never leaves the development machine.
- - Set the remote RPC node URL to `https://api.avax-test.network/ext/bc/C/rpc` (for a full list of testnet RPC node urls visit https://docs.bscscan.com/misc-tools-and-utilities/public-rpc-nodes)
+ - See the Avalance [docs](https://docs.avax.network/quickstart/fuji-workflow) and select and HTTPS RPC endpoint.
  - Set the chain ID to `43113` (the correct ID for the Avalanche Fuji testnet)
  - Merge the custom config created above with the generated `evmconnect` config file
 
@@ -59,7 +59,7 @@ ff init avalanche 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url https://api.avax-test.network/ext/bc/C/rpc \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 43113 \
     --connector-config ~/Desktop/evmconnect.yml 
 ```

docs/tutorials/chains/binance_smart_chain.md

@@ -48,7 +48,7 @@ To create a local FireFly development stack and connect it to the Binance Smart
  - Connect to an ethereum network
  - Use the `evmconnect` blockchain connector
  - Use an remote RPC node. This will create a signer locally, so that our signing key never leaves the development machine.
- - Set the remote RPC node URL to `https://data-seed-prebsc-1-s1.binance.org:8545` (for a full list of testnet RPC node urls visit [https://docs.bscscan.com/misc-tools-and-utilities/public-rpc-nodes](https://docs.bscscan.com/misc-tools-and-utilities/public-rpc-nodes))
+ - See the Binance BscScan [docs](https://docs.bscscan.com/misc-tools-and-utilities/public-rpc-nodes) and select an HTTPS RPC endpoint.
  - Set the chain ID to `97` (the correct ID for the Binance Smart Chain testnet)
  - Merge the custom config created above with the generated `evmconnect` config file
 
@@ -59,7 +59,7 @@ ff init bsc 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url https://data-seed-prebsc-1-s1.binance.org:8545 \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 97 \
     --connector-config ~/Desktop/evmconnect.yml 
 ```

docs/tutorials/chains/moonbeam.md

@@ -59,7 +59,7 @@ ff init moonbeam 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url <selected rpc endpoint> \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 1287 \
     --connector-config ~/Desktop/evmconnect.yml 
 ```

docs/tutorials/chains/optimism.md

@@ -48,7 +48,7 @@ To create a local FireFly development stack and connect it to the Optimism testn
  - Connect to an ethereum network
  - Use the `evmconnect` blockchain connector
  - Use an remote RPC node. This will create a signer locally, so that our signing key never leaves the development machine.
- - Set the remote RPC node URL to `https://goerli.optimism.io`
+ - See the optimism [docs](https://community.optimism.io/docs/useful-tools/networks/) and select an HTTPS RPC endpoint.
  - Set the chain ID to `420` (the correct ID for the Optimism testnet)
  - Merge the custom config created above with the generated `evmconnect` config file
 
@@ -59,7 +59,7 @@ ff init optimism 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url https://goerli.optimism.io \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 420 \
     --connector-config ~/Desktop/evmconnect.yml 
 ```

docs/tutorials/chains/polygon_testnet.md

@@ -48,7 +48,7 @@ To create a local FireFly development stack and connect it to the Polygon Mumbai
  - Connect to an ethereum network
  - Use the `evmconnect` blockchain connector
  - Use an remote RPC node. This will create a signer locally, so that our signing key never leaves the development machine.
- - Set the remote RPC node URL to `https://rpc-mumbai.maticvigil.com`
+ - See the polygon [docs](https://docs.polygon.technology/docs/develop/network-details/network/) and select an HTTPS RPC endpoint.
  - Set the chain ID to `80001` (the correct ID for the Polygon Mumbai testnet)
  - Merge the custom config created above with the generated `evmconnect` config file
 
@@ -59,7 +59,7 @@ ff init polygon 1 \
     -b ethereum \
     -c evmconnect \
     -n remote-rpc \
-    --remote-node-url https://rpc-mumbai.maticvigil.com \
+    --remote-node-url <selected RPC endpoint> \
     --chain-id 80001 \
     --connector-config ~/Desktop/evmconnect.yml 
 ```