Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Straight-forward guide to make a new Optimism deployment: L1 contracts deployment, L2 contracts deployment, data transport layer, L2 node #374

Open
vbaranov opened this issue Jan 26, 2022 · 2 comments

Comments

@vbaranov
Copy link

I am trying to make a new Optimism deployment. I started with the deployment of contracts. Following the guide from packages/contracts/README.md, the whole set of contracts is deployed to the L1 network as a result, whereas, I suppose, that contracts prefixed with OVM_ should be deployed to L2. I tried to find mode detailed explanation of each contract, but the related link is broken ethereum-optimism/optimism#2082. Is any straightforward guide how to make a new Optimism deployment to the chain, where it doesn't exist yet: contracts deployment + data transport layer + L2 node?

@vbaranov vbaranov changed the title Following a guide from packages/contracts/README.md, all contracts are deployed to L1 Straight-forward guide to make a new Optimism deployment: L1 contracts deployment, L2 contracts deployment, data transport layer, L2 node Jan 26, 2022
@smartcontracts
Copy link
Collaborator

I agree that we should include a guide for deploying the entire system. Some of our documentation for deploying the contracts is very out of date.

@smartcontracts
Copy link
Collaborator

We've updated the contracts README. I think this issue is better suited for the community-hub which contains all of the docs for Optimism.

@smartcontracts smartcontracts transferred this issue from ethereum-optimism/optimism Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants