[OP Stack Deployment] I want to use bedrock mainnet with Sepolia. is it safe to use version not yet released on Mainnet

[L2nitant]

Issue Description

Initially I was using Bedrock mainnet but because of goerli shutdown I will move to sepolia. I am planning to use https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.1.3 but it is not on mainnet. So will there any security concern regarding that?
And also I don't want to use cannon, but i think this version support cannon upgrade

Additional Information

No response

[sbvegan]

Hey @L2nitant,

That is an older version of our client. The latest releases that are running on mainnet can be found here:

• https://github.com/ethereum-optimism/optimism/releases
• https://github.com/ethereum-optimism/op-geth/releases

We actually recommend you run the latest finalized release. That way you have the latest software that has the latest improvements, features, and is in line with what we're running in production.

Here's a blog post about the fault proof status: The OP Stack's Fault Proof System is live on OP Goerli.

In addition, because the Canyon testnet upgrade just happened, you'll want to make sure to follow these instructions when starting up your node.

[sbvegan]

Yes, we're running the latest releases on those pages on mainnet.

[sbvegan]

cc @L2nitant does this answer your question. Also do you mean cannon or Canyon upgrade?

[L2nitant]

yes that answer my question. I was talking about the canyon. As it is not available for the ethereum mainnet, and in future we have to shift from testnet to mainnet ?
When do you plan to release canyon upgrade for ethereum chain ?

[rohit9888]

One more thing @sbvegan
As we are using latest release, so which op-geth we should follow. One which was in old document or the new one mentioned in stack.optimism.io
Updated Documentation has removed

--password=./datadir/password \
--allow-insecure-unlock \
--miner.etherbase=<SEQUENCER> \
--unlock=<SEQUENCER>

[sbvegan]

@L2nitant the upgrade has to go through a governance vote. It's likely to go live in January 2024.

@rohit9888 you should refer to the new documentation. Those flags are all legacy and should not be used anymore.

[github-actions[bot]]

Hey @L2nitant, 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.