[OP Stack Deployment] Recommended Versions for op-contracts and op-deployer in new chain deployment

[seromenho]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm currently deploying a new Optimism chain and would like clarification on the recommended contract and deployment tool versions.

Questions:

1. op-contracts Version:

   • Should I deploy with op-contracts/v1.8.0 or op-contracts/v1.6.0 and why? (I have seen recommendation to go with op-contracts/v1.6.0 [here])
   • I can see there are new versions, but those are still release candidates. Would you instead recommend something other than 1.8 or 1.6?

2. op-deployer Version:

   • I've seen discussions mentioning potential issues with some op-deployer versions. Could you confirm the recommended op-deployer version to use with the selected op-contracts release? [ref]

3. Deployment Configurations:

   • I intend to deploy with:
     • Alternative Data Availability (Alt-DA) — Are there any available instructions for configuring this setup?
     • No Superchain Integration — I aim to deploy a standalone chain without Superchain features. Could you guide me on the correct setup for this?

Additional Context:

I reviewed the official documentation [here] and [here] but couldn't locate clear instructions specific to Alt-DA and non-Superchain configurations for op-deployer. If there's a preferred resource or example configuration, I'd greatly appreciate the guidance.

I also opened a related discussion about a version and compatibility matrix that could improve clarity regarding deployment best practices. You can find it here:
➡️ Version and Compatibility Matrix Discussion

Thanks in advance for your time and support! 🚀

Logs

No response

Additional Information

No response

Feedback

I also opened a related discussion about a version and compatibility matrix that could improve clarity regarding deployment best practices. You can find it here:
➡️ Version and Compatibility Matrix Discussion

[opfocus]

https://github.com/ethereum-optimism/optimism/releases/tag/op-deployer%2Fv0.0.13 Please pay attention to this release, op-contracts/v1.8.0 is used by default here

[seromenho]

Thank you for pointing out the new release. It seems to have resolved a bug mentioned in the other discussion. I appreciate your guidance on this.

I’m assuming the recommended contracts release is op-contracts/v1.8.0. Please let me know if that’s incorrect.

I have a couple of follow-up questions related to configuration and component versions:

Question 1: op-deployer configuration documentation
It would be helpful to have documentation for op-deployer configurations in a similar format to the deploy-config file, detailing all the possible properties and values for the intent file.

This may exist somewhere already, but I haven’t been able to locate it. I'm particularly interested in settings related to Alt-DA mode and Fault Proofs. If you can point me in the right direction, that would be greatly appreciated.

For example Alt-DA I can infer from the code here

[[chains]]
    # chain config
    [chains.dangerousAltDAConfig]
        useAltDA = true

Question 2: Recommended component versions
Regarding the component versions, I’d like to confirm if I should be targeting the latest versions for each component:

• op-batcher/v1.11.5
• op-node/v1.12.0
• op-geth/v1.101503.0
• op-proposer/v1.10.0
• op-alt-da — (assumed to follow the op-batcher version, in this case, op-batcher/v1.11.5)

Please let me know if this version alignment is correct or if there are any recommended deviations.

Thanks again for your help. I appreciate the support!

[seromenho]

@opfocus Should Alt-DA mode still be supported following the introduction of Fault Proofs, or does this mean Fault Proofs are simply unavailable in this mode?

In the Fault Proofs explainer, I noticed the mention of:

Future improvements: Integration with Fault Proofs

I’m wondering if Alt-DA functionality is still viable as-is or if adjustments are required.

I believe so. There's also this note on the op-contracts/v1.8.0

In addition to the above configuration Fault Proofs release, another L2OutputOracle configuration is supported by this release. When using this set of contracts, the full set of semvers is:

Thank you!

[opfocus]

[[chains]]
    # chain config
    [chains.dangerousAltDAConfig]
        useAltDA = true

I found its data structure here: https://github.com/ethereum-optimism/optimism/blob/098b02464e22e343266ebcec35bcc30ed980c993/op-chain-ops/genesis/config.go#L609

type AltDADeployConfig struct {
	// UseAltDA is a flag that indicates if the system is using op-alt-da
	UseAltDA bool `json:"useAltDA" toml:"useAltDA"`
	// DACommitmentType specifies the allowed commitment
	DACommitmentType string `json:"daCommitmentType" toml:"daCommitmentType"`
	// DAChallengeWindow represents the block interval during which the availability of a data commitment can be challenged.
	DAChallengeWindow uint64 `json:"daChallengeWindow" toml:"daChallengeWindow"`
	// DAResolveWindow represents the block interval during which a data availability challenge can be resolved.
	DAResolveWindow uint64 `json:"daResolveWindow" toml:"daResolveWindow"`
	// DABondSize represents the required bond size to initiate a data availability challenge.
	DABondSize uint64 `json:"daBondSize" toml:"daBondSize"`
	// DAResolverRefundPercentage represents the percentage of the resolving cost to be refunded to the resolver
	// such as 100 means 100% refund.
	DAResolverRefundPercentage uint64 `json:"daResolverRefundPercentage" toml:"daResolverRefundPercentage"`
}

Here is an example for reference: https://docs.availproject.org/docs/build-with-avail/deploy-rollup-on-avail/Optimium/op-stack/op-stack#core-contract-deployment

 "useAltDA": true,
  "daCommitmentType": "GenericCommitment",
  "daChallengeWindow": 160,
  "daResolveWindow": 160,
  "daBondSize": 1000000,
  "daResolverRefundPercentage": 0

We can see the introduction of [globalDeployOverrides] from the documentation: https://docs.optimism.io/operators/chain-operators/tools/op-deployer#deployment-usage

[globalDeployOverrides]
  l2BlockTime = 1 # 1s L2blockTime is also standard, op-deployer defaults to 2s

Question 2:
I think we should always choose the latest version of a component.

There are few instructions on how to use op-deployer to deploy alt-da. Fault-proof should be supported by default. You can pay attention to this PR, which may be helpful:
ethereum-optimism/optimism#12798

Regarding op-contracts/v1.8.0, it supports Holocene network upgrade, which is the latest upgrade on the mainnet. So I think it's appropriate.
The slightly different thing here should be the slightly modified version that supports alt-da.
The last thing to note is the Pectra breaking changes in the documentation （I think we can ignore it for now and just upgrade it at runtime.）: https://docs.optimism.io/notices/pectra-changes#for-fault-proof-enabled-chains

Hope this information helps you, I haven't tried it

[seromenho]

For alt-da seems to be clear. Thank you

But how about Fault Proofs? I want to disable it similar to what you could do with the old deploy config https://docs.optimism.io/operators/chain-operators/configuration/rollup#usefaultproofs
I found this https://github.com/ethereum-optimism/optimism/blob/098b02464e22e343266ebcec35bcc30ed980c993/op-deployer/pkg/deployer/state/deploy_config.go#L106-L113 but how do I override that?
Thank you.

[seromenho]

Side note:
I’ve opened an issue in the docs repo to suggest adding documentation for op-deployer intent file configurations: ethereum-optimism/docs#1505

I believe this would help improve clarity around available properties.

[seromenho]

@opfocus, perhaps something like this?

[globalDeployOverrides]
  [globalDeployOverrides.faultProofDeployConfig]
    useFaultProofs = false

Thank you!

By the way, I’ll be opening a new discussion soon regarding forks of the contracts. Although it might be related, I believe it warrants a separate thread for better clarity and focus.

[opfocus]

https://github.com/ethereum-optimism/optimism/blob/098b02464e22e343266ebcec35bcc30ed980c993/op-deployer/pkg/deployer/pipeline/opchain.go#L73
may have been overridden in the process

[opfocus]

Please open a new discussion to discuss issues related to the contract.
After the discussion is closed, new answers cannot be added, but replies can still be added.