[OP Stack Deployment] op proposer error

[Blue003-dev]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

Hello, I am building an op stack according to the guide at the above URL.
https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup

I am using op-node v1.13.2 and op-geth v1.101503.4 to build a local test op-stack.
However, when I run op-proposer as follows, ./bin/op-proposer
--poll-interval=12s
--rpc.port=8560
--rollup-rpc=http://localhost:9545
--l2oo-address=$(cat ../packages/contracts-bedrock/deployments/getting-started/.deploy | jq -r .L2OutputOracleProxy)
--private-key=0xXXXXXXXXX
--l1-eth-rpc=https://crimson-radial-gadget.ethereum-sepolia.quiknode.pro/XXXXXXXXXXX

output message :

cat: ../packages/contracts-bedrock/deployments/getting-started/.deploy: No such file or directory
t=2025-04-29T05:50:29+0000lvl=crit msg=“Application failed”message=“failed to setup: invalid CLI flags: neither the DisputeGameFactory nor L2OutputOracle address was provided”

The following command appears.
There is no folder or file named getting-started/.deploy under the /packages/contracts-bedrock/deployments folder.

Is there any additional command that needs to be executed besides the ones listed in the guide at
https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup#step-1-deploy-the-l1-contracts

And below is a Korean blog site.
https://blog.naver.com/pjt3591oo/223432855140
If you look at the blog (translated into English),
forge script scripts/Deploy.s.sol:Deploy --private-key $GS_ADMIN_PRIVATE_KEY --broadcast --rpc-url $L1_RPC_URL --slow
The command guide is provided above.

Is the command listed below sufficient for deploying the L1 contract, or do I need to execute an additional command?
https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup

./bin/op-deployer apply --workdir .deployer \ --l1-rpc-url <RPC_URL_FOR_L1> \ --private-key <DEPLOYER_PRIVATE_KEY_HEX>

I would appreciate your help.

The second question is about how to make rollup.json file
According to above blog site, that site guides that type command below.
go run cmd/main.go genesis l2
--deploy-config ../packages/contracts-bedrock/deploy-config/getting-started.json
--l1-deployments ../packages/contracts-bedrock/deployments/getting-started/.deploy
--outfile.l2 genesis.json
--outfile.rollup rollup.json
--l1-rpc $L1_RPC_URL
to generate rollup.json, as mentioned in a personal blog.
Below is original guide at https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup
./bin/op-deployer inspect rollup --workdir .deployer <L2_CHAIN_ID> > .deployer/rollup.json
which command is correct? Could you please confirm if the above commands are correct? Thank you.

Logs

No response

Additional Information

No response

Feedback

No response

[opfocus]

--l2oo-address=$(cat ../packages/contracts-bedrock/deployments/getting-started/.deploy | jq -r .L2OutputOracleProxy)
This command is not applicable to scenarios where op-deployer is used to deploy L1 contracts.
Please refer to https://docs.optimism.io/operators/chain-operators/tools/op-deployer to use op-deployer

Regarding the startup of the component, please refer to it (note that the component content here is incomplete and is for reference only) #17 (comment)

[yohanelly95]

@opfocus so using op-deployer is now the best way to deploy contracts for OP stack chains including testnet and mainnet?

[Chomtana]

Yes, the old deploy from contracts source code is deprecated.

[yohanelly95]

@Chomtana understood! is there a sample intent.toml I could refer too ? will be spinning up an L3.

[yohanelly95]

was unsure about the following values, but Ive set them too

  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  operatorFeeScalar = 0
  operatorFeeConstant = 0

not sure if this ideal for an L3

[Chomtana]

Doc is invalid because it has been mixed up

You should use op-deployer to deploy contracts and use the lastest release branch in https://github.com/ethereum-optimism/optimism/releases

And in the op-proposer step, instead of --l2oo-address=... you should use --game-factory-address=0x... and find the dispute game factory address from command ./bin/op-deployer inspect l1 --workdir .deployer <l2-chain-id>