Skip to content

Commit 95ee134

Browse files
authored
Merge pull request ethereum-optimism#107 from ethereum-optimism/20220602-fix-getting-started
fix(getting-started): How to move to mainnet
2 parents 4d2a113 + e37dd5b commit 95ee134

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

getting-started/README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -310,6 +310,14 @@ The tutorial makes these assumptions:
310310
311311
Note that in the tutorial we've been compiling smart contracts using [Waffle](https://github.com/TrueFiEng/Waffle). If you prefer to compile your smart contracts using other tools (like [Hardhat](https://hardhat.org/)) you can install the appropriate packages and modify `build` script in the `package.json` file.
312312

313+
## Moving to mainnet
314+
315+
When it is time to deploy your application on mainnet, follow these steps:
316+
317+
1. Use [a bridge](https://app.optimism.io/bridge) to transfer ETH to Optimism mainnet.
318+
1. Where you specify the RCP endpoint URL, use [a mainnet endpoint](https://community.optimism.io/docs/useful-tools/networks/#optimism-mainnet).
319+
320+
313321
## Best practices
314322

315323
It is best to start development with the EVM provided by the development stack.
@@ -319,3 +327,4 @@ After you are done with that development, debug your decentralized application u
319327
This lets you debug parts that that are Optimism specific such as calls to bridges to transfer assets between layers.
320328

321329
Only when you have a version that works well on a test network should you deploy to the production network, where every transaction has a cost.
330+

0 commit comments

Comments
 (0)