Jan 24

components/calculator/ChainParametersForm.tsx

@@ -23,7 +23,7 @@ type DataAvailabilityType = "Ethereum" | "AltDA Plasma Mode";
 export function ChainParametersForm(): ReactElement {
   const [transactionsPerDay, setTransactionsPerDay] = useState(500000);
   const [comparableTransactionType, setComparableTransactionType] =
-    useState<ComparableTransactionType>("General OP Mainnet");
+    useState<ComparableTransactionType>("General Metal L2");
   const [dataAvailabilityType, setDataAvailabilityType] = useState<DataAvailabilityType>("Ethereum");
   const [isFaultProofEnabled, setIsFaultProofEnabled] = useState("yes");
   const [targetDataFeeMargin, setTargetDataFeeMargin] = useState(5);
@@ -36,7 +36,7 @@ export function ChainParametersForm(): ReactElement {
   const [showResult, setShowResult] = useState(false);
 
   const comparableTransactionTypeOptions = [
-    "General OP Mainnet",
+    "General Metal L2",
     "Base",
     "Zora",
     "Mint",

nouns.txt

@@ -1,5 +1,5 @@
 Optimism
-OP Mainnet
+Metal L2
 Ethereum
 OP Stack
 MetaMask

pages/_meta.json

@@ -92,7 +92,7 @@
   },
 
   "chain": {
-    "title": "OP Mainnet",
+    "title": "Metal L2",
     "display": "children"
   },
 

pages/builders/app-developers/bridging/custom-bridge.mdx

@@ -1,7 +1,7 @@
 ---
 title: Custom bridges
 lang: en-US
-description: Important considerations when building custom bridges for OP Mainnet.
+description: Important considerations when building custom bridges for Metal L2.
 ---
 
 import { Callout } from 'nextra/components'
@@ -33,12 +33,5 @@ You can read more about the design of the Standard Bridge in the guide on [Using
 
 The [Superchain Token List](/chain/tokenlist) exists to help users and developers find the right bridged representations of tokens native to another blockchain.
 Once you've built and tested your custom bridge, make sure to register any tokens meant to flow through this bridge by [making a pull request against the Superchain Token List repository](https://github.com/ethereum-optimism/ethereum-optimism.github.io#adding-a-token-to-the-list).
-You **must** deploy your bridge to OP Sepolia before it can be added to the Superchain Token List.
+You **must** deploy your bridge to Metal L2 Testnet before it can be added to the Superchain Token List.
 
-## Next steps
-
-You can explore several examples of custom bridges for OP Mainnet:
-
-*   [NFT Bridge](https://github.com/ethereum-optimism/optimism/blob/v1.1.4/packages/contracts-bedrock/src/L1/L1ERC721Bridge.sol)
-*   [L2 DAI Token Bridge](https://optimistic.etherscan.io/address/0x467194771dae2967aef3ecbedd3bf9a310c76c65#code) and [deployed addresses](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/data/DAI/data.json)
-*   [SNX Bridge](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/data/SNX/data.json)

pages/builders/app-developers/bridging/messaging.mdx

@@ -8,7 +8,7 @@ import { Callout } from 'nextra/components'
 
 # Sending data between L1 and L2
 
-Smart contracts on L1 (Ethereum) can interact with smart contracts on L2 (OP Mainnet) through a process called "bridging".
+Smart contracts on L1 (Ethereum) can interact with smart contracts on L2 (Metal L2) through a process called "bridging".
 This page explains how bridging works, how to use it, and what to watch out for.
 
 <Callout type="info">
@@ -18,8 +18,8 @@ This page explains how bridging works, how to use it, and what to watch out for.
 
 ## Understanding contract calls
 
-It can be easier to understand bridging if you first have a basic understanding of how contracts on EVM-based blockchains like OP Mainnet and Ethereum communicate within the *same* network.
-The interface for sending messages *between* Ethereum and OP Mainnet is designed to mimic the standard contract communication interface as much as possible.
+It can be easier to understand bridging if you first have a basic understanding of how contracts on EVM-based blockchains like Metal L2 and Ethereum communicate within the *same* network.
+The interface for sending messages *between* Ethereum and Metal L2 is designed to mimic the standard contract communication interface as much as possible.
 
 Here's how a contract on Ethereum might trigger a function within another contract on Ethereum:
 
@@ -89,7 +89,7 @@ address(_target).call{gas: _minGasLimit}(_message);
 Except, of course, that you're calling a contract on a completely different network.
 
 This is glossing over a lot of the technical details that make this whole thing work under the hood, but this should be enough to get you started.
-Want to call a contract on OP Mainnet from a contract on Ethereum?
+Want to call a contract on Metal L2 from a contract on Ethereum?
 It's dead simple:
 
 ```solidity
@@ -118,22 +118,22 @@ contract MyContract {
 ```
 
 <Callout type="info">
-  You can find the addresses of the `L1CrossDomainMessenger` and the `L2CrossDomainMessenger` contracts on OP Mainnet and OP Sepolia on the [Contract Addresses](/chain/addresses) page.
+  You can find the addresses of the `L1CrossDomainMessenger` and the `L2CrossDomainMessenger` contracts on Metal L2 and Metal L2 Testnet on the [Contract Addresses](/chain/addresses) page.
 </Callout>
 
 ## Communication speed
 
-Unlike calls between contracts on the same blockchain, calls between Ethereum and OP Mainnet are *not* instantaneous.
+Unlike calls between contracts on the same blockchain, calls between Ethereum and Metal L2 are *not* instantaneous.
 The speed of a cross-chain transaction depends on the direction in which the transaction is sent.
 
 ### For L1 to L2 transactions
 
-Transactions sent from L1 to L2 take **approximately 1-3 minutes** to get from Ethereum to OP Mainnet, or from Sepolia to OP Sepolia.
+Transactions sent from L1 to L2 take **approximately 1-3 minutes** to get from Ethereum to Metal L2, or from Sepolia to Metal L2 Testnet.
 This is because the Sequencer waits for a certain number of L1 blocks to be created before including L1 to L2 transactions to avoid potentially annoying [reorgs](https://www.alchemy.com/overviews/what-is-a-reorg).
 
 ### For L2 to L1 transactions
 
-Transactions sent from L2 to L1 take **approximately 7 days** to get from OP Mainnet to Ethereum, or from OP Sepolia to Sepolia.
+Transactions sent from L2 to L1 take **approximately 7 days** to get from Metal L2 to Ethereum, or from Metal L2 Testnet to Sepolia.
 This is because the bridge contract on L1 must wait for the L2 state to be *proven* to the L1 chain before it can relay the message.
 
 The process of sending transactions from L2 to L1 involves four distinct steps:
@@ -199,7 +199,7 @@ The amount of L1 gas charged increases when more people are sending L1 to L2 tra
 
 Each message from L2 to L1 requires three transactions:
 
-1.  An L2 transaction that *initiates* the transaction, which is priced the same as any other transaction made on OP Mainnet.
+1.  An L2 transaction that *initiates* the transaction, which is priced the same as any other transaction made on Metal L2.
 
 2.  An L1 transaction that *proves* the transaction.
     This transaction can only be submitted after L2 block, including your L2 transaction, is proposed on L1.

pages/builders/app-developers/bridging/standard-bridge.mdx

@@ -8,10 +8,10 @@ import { Callout, Steps } from 'nextra/components'
 
 # Using the Standard Bridge
 
-The Standard Bridge is a basic token bridging system available on OP Mainnet and all other standard OP Stack chains.
-The Standard Bridge allows you to easily move ETH and most ERC-20 tokens between Ethereum and OP Mainnet.
-Transfers from Ethereum to OP Mainnet via the Standard Bridge are usually completed within 1-3 minutes.
-Transfers from OP Mainnet to Ethereum are completed in 7 days as a result of the [withdrawal challenge period](./messaging#understanding-the-challenge-period).
+The Standard Bridge is a basic token bridging system available on Metal L2 and all other standard OP Stack chains.
+The Standard Bridge allows you to easily move ETH and most ERC-20 tokens between Ethereum and Metal L2.
+Transfers from Ethereum to Metal L2 via the Standard Bridge are usually completed within 1-3 minutes.
+Transfers from Metal L2 to Ethereum are completed in 7 days as a result of the [withdrawal challenge period](./messaging#understanding-the-challenge-period).
 
 The Standard Bridge is fully permissionless and supports standard ERC-20 tokens.
 Other bridging systems also exist that provide different features and security properties.
@@ -23,17 +23,17 @@ You may wish to explore some of these options to find the bridge that works best
 
 ## Design
 
-The Standard Bridge allows users to convert tokens that are native to one chain (like Ethereum) into a representation of those tokens on the other chain (like OP Mainnet).
+The Standard Bridge allows users to convert tokens that are native to one chain (like Ethereum) into a representation of those tokens on the other chain (like Metal L2).
 Users can then convert these bridged representations back into their original native tokens at any time.
 
-This bridging mechanism functions identically in both directions — tokens native to OP Mainnet can be bridged to Ethereum, just like tokens native to Ethereum can be bridged to OP Mainnet.
-Here you'll get to understand how the Standard Bridge works when moving tokens from Ethereum to OP Mainnet.
+This bridging mechanism functions identically in both directions — tokens native to Metal L2 can be bridged to Ethereum, just like tokens native to Ethereum can be bridged to Metal L2.
+Here you'll get to understand how the Standard Bridge works when moving tokens from Ethereum to Metal L2.
 Since the bridging mechanism is mirrored on both sides, this will also explain how the bridge works in the opposite direction.
 
 ### Architecture
 
-The Standard Bridge is composed of two contracts, the [`L1StandardBridge`](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/packages/contracts-bedrock/contracts/L1/L1StandardBridge.sol) (on `Ethereum`) and the [`L2StandardBridge`](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/packages/contracts-bedrock/contracts/L2/L2StandardBridge.sol) (on `OP Mainnet`).
-These two contracts interact with one another via the `CrossDomainMessenger` system for sending messages between Ethereum and OP Mainnet.
+The Standard Bridge is composed of two contracts, the [`L1StandardBridge`](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/packages/contracts-bedrock/contracts/L1/L1StandardBridge.sol) (on `Ethereum`) and the [`L2StandardBridge`](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/packages/contracts-bedrock/contracts/L2/L2StandardBridge.sol) (on `Metal L2`).
+These two contracts interact with one another via the `CrossDomainMessenger` system for sending messages between Ethereum and Metal L2.
 You can read more about the `CrossDomainMessenger` in the guide on [Sending Data Between L1 and L2](./messaging).
 
 ### Bridged tokens
@@ -104,7 +104,7 @@ The process for bridging a native token involves a few steps.
   {<h3>The minting message is executed</h3>}
 
   Once the minting message is sent, it must be relayed to the receiving side.
-  Message relaying is automatic when sending from Ethereum to OP Mainnet but requires additional user transactions when sending from OP Mainnet to Ethereum.
+  Message relaying is automatic when sending from Ethereum to Metal L2 but requires additional user transactions when sending from Metal L2 to Ethereum.
   Read more about the message relaying process in the guide to [Sending Data Between L1 and L2](./messaging#communication-speed).
 
   When the message is relayed, the `finalizeBridgeERC20` function will be triggered on the receiving Standard Bridge contract.
@@ -126,7 +126,7 @@ The process for bridging a native token involves a few steps.
   This is part of the [`IOptimismMintableERC20`](https://github.com/ethereum-optimism/optimism/blob/8ed8be8806208976e63421bd68779477d12295b5/packages/contracts-bedrock/src/universal/IOptimismMintableERC20.sol) interface.
 
   This completes the process of bridging native tokens.
-  This process is identical in both the Ethereum to OP Mainnet and OP Mainnet to Ethereum directions.
+  This process is identical in both the Ethereum to Metal L2 and Metal L2 to Ethereum directions.
 </Steps>
 
 ### Bridging non-native tokens
@@ -139,7 +139,7 @@ The process for bridging a non-native, bridged representation of a token involve
   {<h3>User calls the bridging function</h3>}
 
   Unlike when bridging native tokens, users do not need to provide an approval to trigger a transfer of a bridged token because the Standard Bridge should already have the ability to `burn` these tokens.
-  Here, the user calls the [`bridgeERC20To`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L193-L217) function on the `StandardBridge` contract on the chain where the bridged token lives (e.g., the `L2StandardBridge` contract if the token is bridged to OP Mainnet).
+  Here, the user calls the [`bridgeERC20To`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L193-L217) function on the `StandardBridge` contract on the chain where the bridged token lives (e.g., the `L2StandardBridge` contract if the token is bridged to Metal L2).
 
   The user must provide the following parameters to this function call:
 
@@ -164,7 +164,7 @@ The process for bridging a non-native, bridged representation of a token involve
   {<h3>The unlock message is executed</h3>}
 
   Once the unlock message is sent, it must be relayed to the receiving side.
-  Message relaying is automatic when sending from Ethereum to OP Mainnet but requires additional user transactions when sending from OP Mainnet to Ethereum.
+  Message relaying is automatic when sending from Ethereum to Metal L2 but requires additional user transactions when sending from Metal L2 to Ethereum.
   Read more about the message relaying process in the guide to [Sending Data Between L1 and L2](./messaging#communication-speed).
 
   When the message is relayed, the `finalizeBridgeERC20` function will be triggered on the receiving Standard Bridge contract.
@@ -182,17 +182,17 @@ The process for bridging a non-native, bridged representation of a token involve
   If the unlock message is fully verified, `finalizeBridgeERC20` will [unlock and transfer tokens to the recipient](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L280-L281) equal to the number of tokens originally burned on the other blockchain.
 
   This completes the process of bridging native tokens.
-  This process is identical in both the Ethereum to OP Mainnet and OP Mainnet to Ethereum directions.
+  This process is identical in both the Ethereum to Metal L2 and Metal L2 to Ethereum directions.
 </Steps>
 
 ### Bridging ETH
 
-The Standard Bridge contracts can also be used to bridge ETH from Ethereum to OP Mainnet and vice versa.
+The Standard Bridge contracts can also be used to bridge ETH from Ethereum to Metal L2 and vice versa.
 The ETH bridging process is generally less complex than the ERC-20 bridging process.
 Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L143-L150) or [`bridgeETHTo`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L152-L166) functions on either blockchain.
 
 <Callout>
-  Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`.
+  Users can also deposit ETH from Ethereum to Metal L2 by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`.
   This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function.
   You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page.
 </Callout>
@@ -217,7 +217,7 @@ Tokens on the Superchain Token List will automatically appear on certain tools l
 You should strongly consider using the Superchain Token List to verify that you're using the correct bridged representation of a token when bridging a native token.
 Doing so can help you avoid accidentally bridging to the wrong token and locking up your native token permanently.
 
-You can easily find the bridged representation of a token for OP Mainnet on the [Bridged Token Addresses](/chain/tokenlist#op-mainnet) page.
+You can easily find the bridged representation of a token for Metal L2 on the [Bridged Token Addresses](/chain/tokenlist#op-mainnet) page.
 If you want to find the bridged representation of a token for another chain, use the following steps.
 
 <Steps>

pages/builders/app-developers/quick-start.mdx

@@ -15,8 +15,8 @@ This quick start uses [`Scaffold-OP`](https://github.com/ethereum-optimism/scaff
 
 ## Step 1: Get Testnet ETH from Superchain Faucet
 
-You'll need some testnet ETH on OP Sepolia to pay for the [gas fees](https://ethereum.org/en/developers/docs/gas/) associated with deploying your test application.
-Use the [Optimism Superchain Faucet](https://console.optimism.io/faucet?utm_source=scaffoldop) to get some free ETH on OP Sepolia for multiple OP Chains with just one click.
+You'll need some testnet ETH on Metal L2 Testnet to pay for the [gas fees](https://ethereum.org/en/developers/docs/gas/) associated with deploying your test application.
+Use the [Optimism Superchain Faucet](https://console.optimism.io/faucet?utm_source=scaffoldop) to get some free ETH on Metal L2 Testnet for multiple OP Chains with just one click.
 You can request testnet ETH from the Superchain Faucet in one of two ways: **connect a wallet** or **login with Github**.
 
 <Image src="/img/builders/app-developers/quick-start/faucet-markup.png" alt="Superchain Faucet sign-up options" width={500} height={500} />
@@ -26,7 +26,7 @@ You can request testnet ETH from the Superchain Faucet in one of two ways: **con
 
 <Callout>
   Looking for more faucets?
-  You can also try using [other available OP Sepolia faucets](/builders/tools/build/faucets).
+  You can also try using [other available Metal L2 Testnet faucets](/builders/tools/build/faucets).
 </Callout>
 
 ## Step 2: Build a basic app with Scaffold-OP
@@ -157,7 +157,7 @@ Please ensure you have enough Sepolia ETH on all these Superchains before deploy
   </Callout>
 </Steps>
 
-Congratulations! You now have an OP Mainnet app ready for development, which can also be deployed to more OP Chains! 🎉
+Congratulations! You now have an Metal L2 app ready for development, which can also be deployed to more OP Chains! 🎉
 
 ## Next steps