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

[L2 Testnet Tutorial] Clarification Needed on L1 Contract Deployment Doc #1401

Open
Leoforever123 opened this issue Feb 21, 2025 · 1 comment
Labels
community-request docs updates requested by community or OP collective documentation Improvements or additions to documentation

Comments

@Leoforever123
Copy link

I'm currently working through the "Deploy the L1 contracts" section and came across some confusing points that I'd like to clarify.

Firstly, the documentation recommends using op-deployer, but it still mentions the script-based deployment method without explaining how they coexist or which one should be used. This is a bit confusing for someone trying to follow the process step-by-step.

Secondly, after installing op-deployer, I noticed that there's only an executable file and no bin folder or op-deployer directory as implied in the tutorial. The instructions mention commands like cd op-deployer and ./bin/op-deployer, which don't seem to align with what's actually installed. Since I've already added op-deployer to my PATH, I don't think it should require navigating to a non-existent directory or using the ./bin/ prefix.

I'm new here. If I misunderstand anything, please let me know.😊

@Leoforever123 Leoforever123 added community-request docs updates requested by community or OP collective documentation Improvements or additions to documentation labels Feb 21, 2025
@bradleycamacho
Copy link
Member

Hi @Leoforever123! Thanks for the feedback; I'm gonna tag @krofax who's more familiar with these tutorials.

We'll take a look at getting this updated if needed and get back to you when fixed. Sorry you've had issues with out docs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-request docs updates requested by community or OP collective documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants