[Application Development] I would like to test L2 -> L1 asset transfer.

[ExploitSori]

Did you check the documentation?

• Yes
• No

Documentation Feedback (Optional)

No response

What type of issue are you experiencing?

• Error
• Feature Request
• General Question

Issue Description

I know that optimism uses optimistic rollup to set the challenge period to 7 days. I also know that the testnet has a challenge period set to 7 days.
It takes 7 days to transfer L2 -> L1 assets. This period is too long for me.
I want to reduce the period by setting the challenge period to 604800 seconds.
I used https://github.com/ethereum-optimism/optimism, but there was no way. So I used https://github.com/upnodedev/optimism-package.
However, even with that, the challenge period was set to 604800 in the contract. I want to test the contract using optimistic rollup L2 with a reduced challenge period.
Please let me know if there is a way. I want to make it as simple as possible and I prefer docker.
I want to know a method other than zk Rollup and foundry local test. I want to use optimistic rollup.
I want to focus on contract development

Lastly, I'm curious, are all the other contract developers waiting for 7 days?

Steps to Reproduce

There doesn't seem to be an option to set a challenge period in https://github.com/ethereum-optimism/optimism.
L2 -> L1 asset transfer test, if there is a way, option, or supported chain to reduce the challenge period (7 days), please let me know

Are you using a specific library or SDK?

• OP-SDK
• Viem
• Other
• Not Sure

Are you using the latest version of the library/SDK?

• Yes
• No

Environment Details

optimism v1.13.2 - release
Macbook pro 14 M1 - Sequoia v15.4.1
Docker version 28.1.1, build 4eba377
kurtosis version - CLI Version: 1.8.0

Troubleshooting Attempts

I looked at the official documentation of optimism, but it only tells me about the tutorial branch.
I want to use a version that supports pectra upgrade.
Please help me.

What type of support do you need?

• Technical support for issue resolution
• Feature implementation guidance
• General advice or consultation
• Documentation or learning resources

Additional Information

No response

Feedback

No response

[imtipi]

https://github.com/ethereum-optimism/optimism/tree/develop/kurtosis-devnet
try this devnet,can be set refer to https://github.com/ethpandaops/optimism-package/blob/68d71d7c2ca21a1541199ab34336fb03ae11d282/src/contracts/contract_deployer.star#L237

[jsvisa]

I think maybe you can config the period by set preimageOracleChallengePeriod variable in your config.json, ref https://docs.optimism.io/operators/chain-operators/configuration/rollup#preimageoraclechallengeperiod and https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/deploy-config/sepolia-devnet-0.json#L75

[imtipi]

after my research,i think https://github.com/upnodedev/optimism-package/tree/main is easier to setup a low challenge period devnet

[ExploitSori]

It’s not a complete solution yet, but I was able to resolve the issue to some extent.
All time-related variables in the repository (e.g., 604800 seconds, 302400, etc.) need to be adjusted accordingly.
I hope this note can help those who are implementing L2 → L1 asset transfers.

Also, Optimism has released a one-click deployment system. I’m not sure if this adjustment has already been reflected there:
https://localchain.optimism.io/