You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: getting-started/README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -310,6 +310,14 @@ The tutorial makes these assumptions:
310
310
311
311
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.
312
312
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
+
313
321
## Best practices
314
322
315
323
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
319
327
This lets you debug parts that that are Optimism specific such as calls to bridges to transfer assets between layers.
320
328
321
329
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.
0 commit comments