Merge pull request #194 from ethereum-optimism/qbzzt/230712-sdk-many-chains

feat(*): Add notices that the SDK supports many chains

Author: qbzzt

cross-dom-bridge-erc20/README.md

@@ -7,7 +7,11 @@ This tutorial teaches you how to use the [Optimism SDK](https://sdk.optimism.io/
 While you *could* use [the bridge contracts](https://community.optimism.io/docs/developers/bridge/standard-bridge/) directly, a [simple usage error](https://community.optimism.io/docs/developers/bridge/standard-bridge/#depositing-erc20s) can cause you to lock tokens in the bridge forever and lose their value. 
 The SDK provides transparent safety rails to prevent that mistake.
 
-
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 **Warning:** The standard bridge does *not* support certain ERC-20 configurations:
 

cross-dom-bridge-eth/README.md

@@ -5,7 +5,11 @@
 
 This tutorial teaches you how to use the [Optimism SDK](https://sdk.optimism.io/) to transfer ETH between Layer 1 (Ethereum or Goerli) and Layer 2 (OP Mainnet or OP Goerli).
 
-
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 ## Setup
 

cross-dom-comm/README.md

@@ -165,6 +165,12 @@ The fault challenge window starts after you do this, so it's best to do it as ea
 
 1. Get the SDK (it is already in `node_modules`).
 
+   The SDK supports multiple OP Chains: OP, Base, etc.
+   To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+   Chains that aren't officially supported just take a few extra steps.
+   Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+   Once you do that, you can use the SDK normally.
+
    ```js
    sdk = require("@eth-optimism/sdk")
    ```

sdk-estimate-gas/README.md

@@ -8,7 +8,11 @@ This tutorial teaches you how to use the Optimism SDK to estimate the gas costs
 This calculation is complicated by the fact that the major cost is the cost of writing the transaction on L1, it doesn't work to just multiply the gas used by the transaction by the gas price, the same way you would on L1. 
 [You can read the details of the calculation here](https://help.optimism.io/hc/en-us/articles/4411895794715-Transaction-fees).
 
-
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 ## Prerequisites
 

sdk-trace-tx/README.md

@@ -6,6 +6,12 @@
 This tutorial teaches you how to trace individual cross-domain transactions between L1 Ethereum and OP Mainnet using [the Optimism SDK](https://sdk.optimism.io/).
 To see how to send these messages, see [the cross domain tutorial](../cross-dom-comm/) or the tutorials on how to transfer [ETH](../cross-dom-bridge-eth/) and [ERC-20](../cross-dom-bridge-erc20/).
 
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
+
 ## Getting started
 
 ### Prerequisites

sdk-view-tx/README.md

@@ -6,7 +6,11 @@
 
 This tutorial teaches you how to use [the Optimism SDK](https://sdk.optimism.io/) to view the transactions passed between L1 (Ethereum) and L2 (OP Mainnet) by an address.
 
-
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 
 ## Prerequisites

standard-bridge-custom-token/README.md

@@ -105,6 +105,11 @@ Then the only thing we need to do is call the internal `_setupDecimals(8)` metho
 ### Transfer tokens
 
 Create and use [`CrossDomainMessenger`](https://sdk.optimism.io/classes/crosschainmessenger) (the Optimism SDK object used to bridge assets).
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 1. Import the Optimism SDK.
 

standard-bridge-standard-token/README.md

@@ -124,6 +124,11 @@ If you do not need any special processing on L2, just the ability to deposit, tr
 ### Transfer tokens
 
 Create and use [`CrossDomainMessenger`](https://sdk.optimism.io/classes/crosschainmessenger) (the Optimism SDK object used to bridge assets).
+The SDK supports multiple OP Chains: OP, Base, etc.
+To see whether a specific OP Chain is supported directly, [see the documentation](https://sdk.optimism.io/enums/l2chainid).
+Chains that aren't officially supported just take a few extra steps.
+Get the L1 contract addresses, and [provide them to the SDK](https://stack.optimism.io/docs/build/sdk/#contract-addresses).
+Once you do that, you can use the SDK normally.
 
 1. Import the Optimism SDK.