[OP Stack Deployment] op-proposer startup command and parameter issues

[alowe5579]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

1. Log of running op-proposer:
   INFO [07-07|10:32:18.482] Initializing L2Output Submitter
   INFO [07-07|10:32:19.057] Metrics disabled
   INFO [07-07|10:32:19.336] Connected to DisputeGameFactory address=0xEB362029079DD39a81daa7e609f69D0b2168bba3 version=1.0.1
   INFO [07-07|10:32:19.338] Starting JSON-RPC server
   INFO [07-07|10:32:19.350] Started RPC server endpoint=http://[::]:8560
   INFO [07-07|10:32:19.350] Starting Proposer
   INFO [07-07|10:32:19.350] Starting Proposer
   INFO [07-07|10:32:19.624] rollup current L1 block still behind target, retrying current_l1=8588a9..4a0c55:8692699 target_l1=8,709,032
   INFO [07-07|10:32:30.450] rollup current L1 block still behind target, retrying current_l1=8588a9..4a0c55:8692699 target_l1=8,709,032

What is the problem with "rollup current L1 block still behind target, retrying current_l1=8588a9..4a0c55:8692699 target_l1=8,709,032"?

2. The command for Run op-proposer in 'https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup' is:
   ./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=$GS_PROPOSER_PRIVATE_KEY
   --l1-eth-rpc=$L1_RPC_URL
   but in '[General] troubleshooting resources #17' it is:
   ./bin/op-proposer
   --poll-interval=12s
   --rpc.port=8560
   --rollup-rpc=http://localhost:9545/
   --private-key=$GS_PROPOSER_PRIVATE_KEY
   --l1-eth-rpc=$L1_RPC_URL

l2oo-address doesn't need to be specified anymore?

3. OP_PROPOSER_GAME_FACTORY_ADDRESS, OP_PROPOSER_PROPOSAL_INTERVAL, OP_PROPOSER_GAME_TYPE are all related to the Dispute game. What is the purpose of the Dispute game?

I hope you can provide a detailed response. At present, I feel that these are the only questions I still have. Once I have completed the entire local deployment, I will publish the latest deployment process in its entirety.Thank you!

Logs

No response

Additional Information

No response

Feedback

No response

[opfocus]

What is the problem with "rollup current L1 block still behind target, retrying current_l1=8588a9..4a0c55:8692699 target_l1=8,709,032"?
wait-node-sync Indicates if, during startup, the proposer should wait for the rollup node to sync to the current L1 tip before proceeding with its driver loop. The default value is false. here your config is true(this is suitable)
The problem is that it seems that your L1 genesis hash is very far away, which may mean there is some problem
l2oo-address doesn't need to be specified anymore?
l2oo-address has been deprecated, https://docs.optimism.io/stack/fault-proofs/fp-security
Dispute game. What is the purpose of the Dispute game?
the doc mentioned above contains descriptions

[alowe5579]

Thanks!

1. If OP_PROPOSER_WAIT_NODE_SYNC=true is suitable, what problems would arise if this were set to false?
2. Is there any way to solve "The problem is that it seems that your L1 genesis hash is very far away, which may mean there is some problem" ?
3. What problems will arise if OP_PROPOSER_GAME_FACTORY_ADDRESS, OP_PROPOSER_PROPOSAL_INTERVAL, OP_PROPOSER_GAME_TYPE uses default values instead of custom values?

[opfocus]

If OP_PROPOSER_WAIT_NODE_SYNC=true is suitable, what problems would arise if this were set to false?
The proposer will try to submit without completing synchronization, but will cause another warning (l1 block high is too low)
Is there any way to solve "The problem is that it seems that your L1 genesis hash is very far away, which may mean there is some problem" ?
This doesn't necessarily represent an error, if the op-node log shows normal, you can just wait (usually you deploy the chain and then start it. There shouldn't be that many blocks unsynced.)
What problems will arise if OP_PROPOSER_GAME_FACTORY_ADDRESS, OP_PROPOSER_PROPOSAL_INTERVAL, OP_PROPOSER_GAME_TYPE uses default values instead of custom values?
please read docs, it's not fair to me explain all these for you
https://docs.optimism.io/operators/chain-operators/configuration/proposer

[alowe5579]

Thanks!