[OP Stack Deployment] basic install

[astro44]

Issue Description

Running through instructions found on https://stack.optimism.io/docs/build/getting-started/#build-the-optimism-monorepo
when running:
pnpm build
errors with nx:
nx run @eth-optimism/contracts-bedrock:build
Could not find 'nx' module in this workspace. Error: [readCachedProjectGraph] ERROR: No cached ProjectGraph is available.
nx run @eth-optimism/core-utils:build
Could not find 'nx' module in this workspace. Error: [readCachedProjectGraph] ERROR: No cached ProjectGraph is available.

Additional Information

I have the below nx:

NX Report complete - copy this into the issue template

Node : 21.3.0
OS : darwin-arm64
pnpm : 8.11.0

nx (global) : 17.1.3
nx : 17.1.3
nx-cloud : 16.5.2
typescript : 5.3.2

and from your script:
./packages/contracts-bedrock/scripts/getting-started/versions.sh
Dependency | Minimum | Actual
git 2 2.41.0
go 1.21 1.21.4
node 20 21.3.0
pnpm 8 8.11.0
foundry 0.2.0 0.2.0
make 3 4.4.1
jq 1.6 1.7
direnv 2 2.33.0

[astro44]

without success on the osX, moved to docker and got passed the earlier issues:

now the roadblock is tied to the forge script:
forge script scripts/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL

8.143 == Logs == 8.143 Connected to network with chainid 11155111 8.143 Storing temp deployment data in /optimism/packages/contracts-bedrock/deployments/sepolia/.deploy 8.143 DeployConfig: reading file /optimism/packages/contracts-bedrock/deploy-config/sepolia.json 8.143 Deploying from Deploy 8.143 Deployment context: sepolia 8.143 Deploying a fresh OP Stack including SuperchainConfig 8.143 Deploying Safe 8.143 New SystemOwnerSafe deployed at 0xE6836005d1e72CC97Fe948FE1e5B01D75aB2C423 8.143 Setting up Superchain 8.143 Deploying AddressManager 8.143 AddressManager deployed at 0x082aa1F6A98864BC66F92c7ceBE774A94873f14D 8.143 Deploying ProxyAdmin 8.143 ProxyAdmin deployed at 0x442865a34d407CD89034d985cDB9519B327AD4f2 8.143 ProxyAdmin ownership transferred to Safe at: 0xE6836005d1e72CC97Fe948FE1e5B01D75aB2C423 8.143 Deploying ERC1967 proxy forSuperchainConfigProxy 8.143 at 0x265EC034F4014985a12bd4D841b4Fa05C6D0896F 8.174 Error: 8.174 script failed: <no data>

any ideas where to look to understand the issue?

thanks.

[opfocus]

From the logs, it appears that the path /optimism/packages/contracts-bedrock/deploy-config/sepolia.json is incorrect; it should be getting-started.json. I was able to run it two days ago on Ubuntu 22.04. You can try echo $DEPLOYMENT_CONTEXT to see if it prints 'getting-started.' Despite successful prints, some users are still reporting this issue. The problem may be that the contract deployment script is not successfully reading DEPLOYMENT_CONTEXT. Please try printing this value and then let's continue the discussion.

[astro44]

@opfocus thanks!
I was able to get it to reflect getting-started.json, and still hitting similar "script failed: no data"
8.184 == Logs ==
8.184 Connected to network with chainid 11155111
8.184 Storing temp deployment data in /optimism/packages/contracts-bedrock/deployments/getting-started/.deploy
8.184 DeployConfig: reading file /optimism/packages/contracts-bedrock/deploy-config/getting-started.json
8.184 Deploying from Deploy
8.184 Deployment context: getting-started
8.184 Deploying a fresh OP Stack including SuperchainConfig
8.184 Deploying Safe
8.184 New SystemOwnerSafe deployed at 0x7331e763974a61e8CD20EF538487c5D39442f472
8.184 Setting up Superchain
8.184 Deploying AddressManager
8.184 AddressManager deployed at 0x082aa1F6A98864BC66F92c7ceBE774A94873f14D
8.184 Deploying ProxyAdmin
8.184 ProxyAdmin deployed at 0x442865a34d407CD89034d985cDB9519B327AD4f2
8.184 ProxyAdmin ownership transferred to Safe at: 0x7331e763974a61e8CD20EF538487c5D39442f472
8.184 Deploying ERC1967 proxy forSuperchainConfigProxy
8.184 at 0x265EC034F4014985a12bd4D841b4Fa05C6D0896F
8.215 Error:
8.215 script failed:

thanks again

[opfocus]

Run 'direnv allow' again in the 'optimism' directory, then try again.

[astro44]

Ok, got it working by statically adding the IMPL_SALT since docker wont' allow dynamic operations like direnv allow.
so now looks like I just need funding are these the wallets I need to fund? or is there a different address missing?:
.....11.77 (code: -32000, message: insufficient funds for gas * price + value: balance 0, tx cost 1026398280528230, overshot 1026398280528230, data: None)
GS_ADMIN_ADDRESS=0x867C5F0537A85fb1A948961D1f1c1e64a773E00F
GS_BATCHER_ADDRESS=0x95aCE797246c061a79Ee52263828C9a8A55b9f78
GS_PROPOSER_ADDRESS=0x5cac6F4eEF9293BF0bc8a833a39BC58d662d3C3A
GS_SEQUENCER_ADDRESS=0x02c0E24D926B2851bF591905259A325ecAaE666f
thanks again!

[opfocus]

before depoy L1 contracts (forge script scripts/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL) need fund to admin account. before start batcher and proposer need fund to bather and proposer

[astro44]

tried:
RUN cd /optimism/packages/contracts-bedrock
&& forge script scripts/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL
&& forge script scripts/Deploy.s.sol:Deploy --private-key $GS_BATCHER_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL
&& forge script scripts/Deploy.s.sol:Deploy --private-key $GS_PROPOSER_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL

still got:
12.37 (code: -32000, message: insufficient funds for gas * price + value: balance 0, tx cost 2327121470951776, overshot 2327121470951776, data: None)

[opfocus]

Only the first one（forge script scripts/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL） is needed. Please check the ETH balance of your admin account; a minimum of 0.2 ETH is required.

[sbvegan]

Thank you @opfocus! In addition, we're migrating the stack docs to here. These docs will be getting the most up to date information and we'll be spinning down stack.optimism.io soon.

[astro44]

@sbvegan Thanks, I'll review this new home for docs.

[github-actions[bot]]

Hey @astro44, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.