[OP Stack Deployment] Deploy chain with Alt-DA + L2OutputOracle (fault proofs disabled) op-contracts/v1.8.0 op-deployer/v0.0.13

[seromenho]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm trying to deploy an OP Stack chain with a specific configuration: Alt-DA enabled, fault proofs disabled, and using L2OutputOracle. However, I'm encountering issues where the deployment process seems always to deploy the fault proof contracts despite my configuration.
Here's the relevant part of my intent.toml file:

configType = "standard-overrides"
l1ChainID = 11155111
fundDevAccounts = true
useInterop = false
l1ContractsLocator = "tag://op-contracts/v1.8.0-rc.4" # L1 smart contracts versions
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts" # L2 smart contracts versions

[[chains]]
  id = "0x000000000000000000000000000000000000000000000000000000000000a455"
  baseFeeVaultRecipient = "0x..."
  l1FeeVaultRecipient = "0x..."
  sequencerFeeVaultRecipient = "0x..."
  eip1559DenominatorCanyon = 250
  eip1559Denominator = 50
  eip1559Elasticity = 6
  [chains.roles]
    l1ProxyAdminOwner = "0x..."
    l2ProxyAdminOwner = "0x..."
    systemConfigOwner = "0x..."
    unsafeBlockSigner = "0x..."
    batcher = "0x..."
    proposer = "0x..."
    challenger = "0x..."
  [chains.dangerousAltDAConfig]
    useAltDA = true
    daCommitmentType = "KeccakCommitment"
    daChallengeWindow = 16
    daResolveWindow = 16
    daBondSize = 1000000
    daResolverRefundPercentage = 0

[globalDeployOverrides]
  useFaultProofs = false
  l2OutputOracleSubmissionInterval = 1800
  l2OutputOracleProposer = "0x..."
  l2OutputOracleChallenger = "0x..."

After running the deployment, I can see that both the fault proof contracts (DisputeGameFactory, FaultDisputeGame, etc.) are deployed, but the L2OutputOracle is not deployed, despite setting useFaultProofs = false

Questions:

1. Is it possible to use op-deployer to create a chain with Alt-DA + L2OutputOracle (fault proofs disabled)? Does version op-deployer/v0.0.13 of op-deployer support this configuration? How?
2. What is the expected behaviour when setting useFaultProofs = false? Should this deploy L2OutputOracle, or is additional configuration required?

Thank you

Logs

No response

Additional Information

No response

Feedback

It would be helpful to have:

1. Clear documentation on the compatibility between Alt-DA mode and L2OutputOracle for the latest (non-RC) version of the contracts.
2. Examples of working intent.toml configurations for different chain setups (standard, Alt-DA with fault proofs, Alt-DA without fault proofs, etc.)
   non-RC

[opfocus]

https://github.com/ethereum-optimism/optimism/blob/backports/op-deployer/v0.0.13/packages/contracts-bedrock/scripts/deploy/DeployImplementations.s.sol
Looks like it only supports fault-proof
In the script logic it uses a fixed salt, so it is checking whether the contract has been deployed, which is already deployed by default.
From the above code, we see that only _name: "OptimismPortal2" appears in the script, which is a contract that only supports fault-proof.
Comparing the code below, we can see:
https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0/packages/contracts-bedrock/scripts/deploy/Deploy.s.sol#L286 Two versions of the OptimismPortal contract will be deployed.
Since op-deployer's script is different, it does not try to deploy the OptimismPortal.

[opfocus]

Can you share your get-started config.json? I plan to try it in the next two days.
You can remove parts of sensitive information

[seromenho]

Sure, here it is: Thank you

{
  "l1StartingBlockTag": "0x8a8f8d0964c85cbce723d959e55f436084908df722ceaab85ecc5533d089e5a0",
  "l1ChainID": 11155111,
  "l2ChainID": 42069,
  "l2BlockTime": 2,
  "l1BlockTime": 12,
  "maxSequencerDrift": 600,
  "sequencerWindowSize": 3600,
  "channelTimeout": 300,
  "p2pSequencerAddress": "0x...",
  "batchInboxAddress": "0x...",
  "batchSenderAddress": "0x...",
  "l2OutputOracleSubmissionInterval": 120,
  "l2OutputOracleStartingBlockNumber": 0,
  "l2OutputOracleStartingTimestamp": 1715000000,
  "l2OutputOracleProposer": "0x...",
  "l2OutputOracleChallenger": "0x...",
  "finalizationPeriodSeconds": 12,
  "proxyAdminOwner": "0x...",
  "baseFeeVaultRecipient": "0x...",
  "l1FeeVaultRecipient": "0x...",
  "sequencerFeeVaultRecipient": "0x...",
  "finalSystemOwner": "0x...",
  "superchainConfigGuardian": "0x...",
  "baseFeeVaultMinimumWithdrawalAmount": "0x8ac7230489e80000",
  "l1FeeVaultMinimumWithdrawalAmount": "0x8ac7230489e80000",
  "sequencerFeeVaultMinimumWithdrawalAmount": "0x8ac7230489e80000",
  "baseFeeVaultWithdrawalNetwork": 0,
  "l1FeeVaultWithdrawalNetwork": 0,
  "sequencerFeeVaultWithdrawalNetwork": 0,
  "gasPriceOracleOverhead": 0,
  "gasPriceOracleScalar": 1000000,
  "enableGovernance": true,
  "governanceTokenSymbol": "OP",
  "governanceTokenName": "Optimism",
  "governanceTokenOwner": "0x...",
  "l2GenesisBlockGasLimit": "0x1c9c380",
  "l2GenesisBlockBaseFeePerGas": "0x3b9aca00",
  "eip1559Denominator": 50,
  "eip1559DenominatorCanyon": 250,
  "eip1559Elasticity": 6,
  "l2GenesisFjordTimeOffset": "0x0",
  "l2GenesisRegolithTimeOffset": "0x0",
  "l2GenesisEcotoneTimeOffset": "0x0",
  "l2GenesisDeltaTimeOffset": "0x0",
  "l2GenesisCanyonTimeOffset": "0x0",
  "systemConfigStartBlock": 0,
  "requiredProtocolVersion": "0x0000000000000000000000000000000000000000000000000000000000000001",
  "recommendedProtocolVersion": "0x0000000000000000000000000000000000000000000000000000000000000001",
  "faultGameAbsolutePrestate": "0x03c7ae758795765c6664a5d39bf63841c71ff191e9189522bad8ebff5d4eca98",
  "faultGameMaxDepth": 44,
  "faultGameClockExtension": 0,
  "faultGameMaxClockDuration": 1200,
  "faultGameGenesisBlock": 0,
  "faultGameGenesisOutputRoot": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "faultGameSplitDepth": 14,
  "faultGameWithdrawalDelay": 600,
  "preimageOracleMinProposalSize": 1800000,
  "preimageOracleChallengePeriod": 300,
  "proofMaturityDelaySeconds": 12,
  "disputeGameFinalityDelaySeconds": 6,
  "respectedGameType": 254,
  "useFaultProofs": false,
  "useAltDA": true,
  "daCommitmentType": "KeccakCommitment",
  "daChallengeWindow": 16,
  "daResolveWindow": 16,
  "daBondSize": 1000000,
  "daResolverRefundPercentage": 0,
  "fundDevAccounts": true
}

[opfocus]

025-03-26T08:21:50.781019Z ERROR forge_script::transaction: Failed to decode constructor arguments contract=Some("AnchorStateRegistry") signature=constructor(address) is_create2=true constructor_args=fea164736f6c634300080f000a
Error: ABI decoding failed: buffer overrun while deserializin   

I also encountered this problem and we are checking it
As another option is https://docs.availproject.org/docs/build-with-avail/deploy-rollup-on-avail/Optimium/op-stack/op-stack#network-configuration-and-setup
I've tried this before and it completed the deployment. But it may not meet your requirements.

[seromenho]

I stumbled upon permissioned fault proofs in superchain-registry issue #857, and it got me exploring this path further.

I looked into the available dispute game types here:
https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/dispute/lib/Types.sol#L51-L83

Then I noticed that deploying with [email protected] sets the game type to 1 (PERMISSIONED_CANNON) — as mentioned by you in this discussion comment, flagged as an issue but it’s actually close to what I’m trying to achieve.

It seems Fault Proofs doesn't work yet with Ald-DA mode: https://docs.optimism.io/stack/beta-features/alt-da-mode#future-improvements
This setup seems to give me exactly what I’m after:

• ✅ Fault proofs are effectively disabled (not to be used), since only a specific challenger (me) is allowed
• ✅ Alt-DA mode is active
• ✅ I’ve tested the chain with this config and confirmed:
  • ✅ ETH Deposit (direct to bridge)
  • ✅ ETH Deposit (via contract call)
  • ✅ ETH Withdrawal (confirmed via prove step using state from the dispute game)

It seems Fault Proofs aren’t fully compatible with Alt-DA mode yet (docs), but more specifically, it’s the dispute process that doesn’t work. If no one ever challenges, the chain can still operate normally. Correct?

What do you think about this approach? Would you consider this a valid (or supported) setup that just want L1 <-> L2 message passing without full fault proof?

[opfocus]

I'm Bella/baoki from the OP Collective working on improving our Developer products.

The mission is to gather some dev insights and I would definitely appreciate messages or a quick scheduled feedback sessions with anyone interested in giving me the inside scoop. We want to get a better sense of what motivates you to build, what works well (what doesn't) and what you want to see improve. If you or any developers you know are interested please message or book a slot using
https://calendar.app.google/5eZNoyKyoJefy7XP9.

Looking forward to talking yall! :heartop:

If you are interested, you can book a slot

[Sledro]

This seems unresolved. Any update?

[kimson99]

Also interested in this issue, currently running a rollup chain with this setting in intent.toml.

[globalDeployOverrides]
  faultGameWithdrawalDelay = 3600
  disputeGameFinalityDelaySeconds = 3600
  useFaultProofs = false

I cannot withdraw from L2 to L1. Encountered this error on calling finalizeWithdrawalTransaction

cause: ContractFunctionRevertedError: The contract function “finalizeWithdrawalTransaction” reverted with the following reason:
OptimismPortal: output proposal has not been validated

It seems fault proof is not disabled. I'm also using op-deployer-0.0.13 and op-contracts/v1.8.0-rc.4.

Any recommendation or example on how to get this working?

Much appreciated.

[opfocus]

@9mmDev #17 (comment) This is what I tried a long time ago, and I'm sure it's out of date. I hope it gives you some reference on the configurations you need to consider.

[kimson99]

@9mmDev As I said above, I didn't start op-challenger. Instead, I did my withdrawal manually following @opfocus instructions

[9mmDev]

@9mmDev #17 (comment) This is what I tried a long time ago, and I'm sure it's out of date. I hope it gives you some reference on the configurations you need to consider.

Have tried that runned, my op-node with --safedb.path=./db/ flag and also running op-dispute-mon , the 'failed to get safe head at l1 block 0x151116a: safe head database not enabled" error is gone, but i am still getting error ProposalNotValidated() while calling checkWithdrawal on OptimismPortalProxy Contract.

Here are commands i used to start op-node, op-challenger , and op-dispute-mon

nohup ./bin/op-node
--l2=$L2_RPC_URL
--l2.jwt-secret=./jwt.txt
--sequencer.enabled
--sequencer.l1-confs=5
--verifier.l1-confs=6
--rollup.config=./rollup.json
--rpc.addr=0.0.0.0
--rpc.enable-admin
--l1=$L1_RPC_URL
--p2p.disable
--l1.rpckind=$L1_RPC_KIND
--l1.beacon=$L1_BEACON_URL
--safedb.path=./db/
--metrics.enabled
--metrics.addr=0.0.0.0
--metrics.port=7300 \

logs/op-node.log 2>&1 &

nohup ./op-challenger/bin/op-challenger
--trace-type=permissioned
--l1-eth-rpc=$L1_RPC_URL
--rollup-rpc=http://localhost:9545
--game-factory-address=0x6d1ed68ea0b89554a1f39c1c8c28ca771601bc9c
--datadir=./op-challenger/datadir
--l2-eth-rpc=$L2_RPC_URL
--num-confirmations=1
--l1-beacon=https://pulsechain-testnet-beacon-api.publicnode.com
--cannon-rollup-config=$(realpath ./op-program/chainconfig/configs/94258-rollup.json)
--cannon-l2-genesis=$(realpath ./op-program/chainconfig/configs/94258-genesis-l2.json)
--cannon-prestate=$(realpath ./op-program/bin/prestate.bin.gz)
--cannon-server ./op-program/bin/op-program
--cannon-bin ./cannon/bin/cannon
--http-poll-interval=15s
--private-key $GS_CHALLENGER_PRIVATE_KEY
--log.level info \

op-challenger/logs/op-challenger.log 2>&1 &
tail -f op-challenger/logs/op-challenger.log

nohup ./op-dispute-mon/bin/op-dispute-mon
--game-factory-address 0x6d1ed68ea0b89554a1f39c1c8c28ca771601bc9c
--l1-eth-rpc $L1_RPC_URL
--rollup-rpc http://localhost:9545 \

op-dispute-mon/logs/op-dispute-mon.log 2>&1 &

None of my withdrawls get finalize

[opfocus]

OptimismPortalProxy please read your this contract method: proofMatrityDelaySeconds and disputeGameFinalityDelaySeconds maybe you need wait @9mmDev

[9mmDev]

OptimismPortalProxy please read your this contract method: proofMatrityDelaySeconds and disputeGameFinalityDelaySeconds maybe you need wait @9mmDev
I can understand but why i have to manually change the status of game from 0 ---> 2 , I am running op-challenger & op-dispute-mon , it running without any issues.