[OP Stack Deployment] What is the latest Alt-Da enabled contract versions?

[Sledro]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

We want to deploy op-stack with alt-da mode enabled using GenericCommitment.

• What is the latest version of the contracts that supports alt-da GenericCommitment?
• Is L2OutputOracle required for alt-da GenericCommitment?
• Should we use the legacy deploy method or op-deployer?

Logs

No response

Additional Information

No response

Feedback

• Additional information relating to alt-da compatible contract versions & deployment in the docs would be good

[Chomtana]

What is the latest version of the contracts that supports alt-da GenericCommitment?

I think you can find latest one with op-contracts/* release on https://github.com/ethereum-optimism/optimism/releases

Latest one is https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv3.0.0

Is L2OutputOracle required for alt-da GenericCommitment?

No, L2OutputOracle is deprecated by Fault Dispute Game and it has nothing to do with the DA because it manage proposing output not batching transactions

Should we use the legacy deploy method or op-deployer?

You should use op-deployer

You can set these Alt-DA deployment configs in the [globalDeployOverrides] section of the intent file

You have to follow docs of your DA provider on how to setup a DA server and how to configure the challenger properly

Note that op-deployer only manage contract deployment. So, when you launch op-node and op-batcher, make sure you follow this document: https://docs.optimism.io/operators/chain-operators/features/alt-da-mode

[Sledro]

L2OutputOracle is deprecated by the fault dispute game, which does not support alt-da according to the docs.

With the upgrade to the Fault Proof Alpha Chad system, output proposals are no longer sent to the L2OutputOracle, but to the DisputeGameFactory in order to be fault proven.

Does this mean that for alt-da:

1. Outputs are still sent to L1, allowing withdrawals to continue.
2. The output can not be challenged as the fraud proofs are not working. (same as L2OutputOracle setup)
3. This would mean we don't require a challenger, dispute-mon etc

Should fault proofs be disabled?

...
  [chains.dangerousAltDAConfig]
    useAltDA = true  # UseAltDA is a flag that indicates if the system is using op-alt-da
    daCommitmentType = "GenericCommitment"  # DACommitmentType specifies the allowed commitment types
    daChallengeWindow = 160 # DAChallengeWindow represents the block interval during which the availability of a data commitment can be challenged
    daResolveWindow = 160 # DAResolveWindow represents the block interval during which a data availability challenge can be resolved.
    daBondSize = 1000000 # DABondSize represents the required bond size to initiate a data availability challenge.
    daResolverRefundPercentage = 0 # DAResolverRefundPercentage represents the percentage of the resolving cost to be refunded to the resolver such as 100 means 100% refund.
[globalDeployOverrides]
    useFaultProofs = false

[opfocus]

[globalDeployOverrides]
    useFaultProofs = false

This configuration most likely won't work. maybe you need delete it
You should be able to deploy it using op-deployer, we have received reports of successful deployments
You still need to run op-challenger, but dispute-mon is not required

Also I think you can still follow https://docs.availproject.org/docs/build-with-avail/deploy-rollup-on-avail/Optimium/op-stack/op-stack to use L2OutputOracle, be aware that it looks a bit outdated and you may need the latest component version to start your chain. However, considering that alt-da is in the experimental stage, there is currently no latest specially optimized version.

[opfocus]

remember set configType = "custom" in intent.toml

[opfocus]

We will close this discussion. If you encounter new issues with your deployment, please open a new discussion. we will discuss new issue there