test: remove release please test, as it is uneeded

[zapper-95]

• The purpose of this repo is for the UpRoll CLI to clone it. It is not designed to be standalone package with releases. We therefore do not require automatic releases made by release-please.

[ExploitSori]

Hello, I have a question about the project, so I'm leaving a comment.
What I want to do is reducing the challenge time of L2 from 604800 seconds to 300 seconds. This is to reducing the test time for rolling up L2 -> L1.
So I changed optimism_package.chains.network_params.withdrawal_delay in network_params.yaml from 604800 to 300, optimism_package.chains.network_params.dispute_game_finality_delay 302400 to 150 .
The chain seems to be running fine, but when I call proofMaturityDelaySeconds()(uint256) on "optimismPortalProxyAddress", 604800 is printed. and "disputeGameFinalityDelaySeconds()(uint256)" 302400 returned.
I think there is a problem with the asset transfer from L2 -> L1. Is there any problem?
Thank you for making it.
Ps. Sorry I cannot speak english well. but I really want to solve this.

[Chomtana]

Hi @ExploitSori are you deploying a new chain with these parameters or are you adjusting these parameters for an existing chain (That you might have just deployed but you set them after you have deployed)

[ExploitSori]

I execute it with kurtosis run . --args-file ./network_params.yaml.

  op_contract_deployer_params:
    image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-deployer:v0.0.12
    l1_artifacts_locator: https://storage.googleapis.com/oplabs-contract-artifacts/artifacts-v1-fffcbb0ebf7f83311791534a41e65ef90df47797f9ca8f86941452f597f7128c.tar.gz
    l2_artifacts_locator: https://storage.googleapis.com/oplabs-contract-artifacts/artifacts-v1-fffcbb0ebf7f83311791534a41e65ef90df47797f9ca8f86941452f597f7128c.tar.gz

It seems that the contracts are deployed with the image and data above. It seems that the contract with the challenge period set to 7 days is deployed in the image.

To change the challenge time, it seems that I need to modify network_params.yaml, set the OptimismPortal2 constructor, deploy it, and then upgrade optimismPortalProxy. Could you please check if this is the right way to do it? Or can I set it separately in kurtosis run . --args-file ./network_params.yaml?

And do I need to redeploy all the contracts related to the challenge time? If you know of any information that needs to be changed, please let me know.

I would like to know how to deploy a contract with a modified challenge time. I don't want to spend a lot of time testing transferring assets from L2 -> L1.

Thanks. @Chomtana

[Chomtana]

I don't think kurtosis can update params of an existing chain at this stage. It's designed for setting initial params of a completely new deployment only.

You might have to redeploy everything not just related contract

[ExploitSori]

I know that the testnet also has a 7 day challenge period. Are all developers waiting 7 days to migrate from L2 to L1?
Are there other testnets or methods of deployment? Are there any testnets with shorter rollup challenge periods other than those using foundry or zk based rollups?
How are other developers working on it?

[Chomtana]

I think it should works with under 7 days.

You could ask about this on https://github.com/ethereum-optimism/developers/discussions there will be more dev looking into

[ExploitSori]

Thank you for your answer. I will talk about it in the place you suggested.

[ExploitSori]

If the @upnodedev team is aware of a solution, I would appreciate it if you could kindly let me know. Please feel free to contact me at your convenience.