[OP Stack Deployment] Deploy my own fork of the op-contracts/v1.8.0 using 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 a chain using a forked version of the op-contracts/v1.8.0 release.

Here's my current configuration:

configType = "standard"
l1ChainID = 11155111
fundDevAccounts = false
useInterop = false
l1ContractsLocator = "file://Users/s/optimism"
l2ContractsLocator = "file://Users/s/optimism"

I’m attempting to use the file:// schema instead of the tag:// schema, as described in the OP Deployer Book, but it doesn’t seem to be working.

Any insights or tips would be greatly appreciated!

Thank you in advance.

Logs

$ op-deployer apply --workdir .deployer --l1-rpc-url  $L1_RPC_URL --private-key $OP_DEPLOYER_PK
Application failed: failed to validate intent-config-type=standard: tag '' not found in standard versions

Additional Information

op-contracts: fork of op-contracts/v1.8.0
op-deployer: `op-deployer/v0.0.13´

No response

Feedback

No response

[imtipi]

#734 (reply in thread)
ethereum-optimism/optimism#14029 (comment)
theres some inconsistent with latest opdeployer
cc @jsvisa please correct me if this isn't applicable

[seromenho]

@imtipi I was attempting this with op-deployer/v0.0.13.

Would you happen to know up to which version of op-deployer the file:// schema was supported for deployments?

Thank you in advance for your help!

[jsvisa]

could you please change into below, and have a retry:
~
diff~ ~-l1ContractsLocator = "file://Users/s/optimism"~ ~-l2ContractsLocator = "file://Users/s/optimism"~ ~+l1ContractsLocator = "file:///Users/s/optimism"~ ~+l2ContractsLocator = "file:///Users/s/optimism"~ ~
~~
after the file:// add the /

You need to change the config type from standard to custom

[jsvisa]

BTW, you need to point the directory into the forge-artifacts, eg:

l1ContractsLocator = "file:///root/op-kurtosis/op-contracts/v1.8.0-rc.4/forge-artifacts"

[seromenho]

Pointing to the forge artifacts directory did the trick! 🎯 Thank you

However, I’m now running into the same issue mentioned here: ethereum-optimism/optimism#14029.

I reviewed the issue and replaced release() with l1ContractsRelease, which helped me bypass that specific error. Unfortunately, a similar error appeared right after, and I’m now wondering how many more issues might surface. 😅

The new error: unrecognized 4 byte signature: 201d2949

At this point, I’m starting to suspect that op-deployer/v0.0.13 may not be fully compatible with deploying op-contracts/v1.8.0 if you need to deploy the implementations. What do you think?

I’ll attempt to fix the next issue and see how things progress.

Current error log:

...
WARN [03-16|23:22:55.540] callframe                                depth=1 byte4=0xfc4dcacb addr=0x551618101B3999B61c266b9B3f8489195d32a328 callsite= label=DeployImplementations
WARN [03-16|23:22:55.540] Revert                                   addr=0x551618101B3999B61c266b9B3f8489195d32a328 label=DeployImplementations err="execution reverted" revertMsg="failed to run ParseTomlAddress_65e7c844, ABI: \"parseTomlAddress(string,string)\", err: key \"releases\" not found in TOML" depth=1
WARN [03-16|23:22:55.565] callframe                                depth=1 byte4=0xfc4dcacb addr=0x551618101B3999B61c266b9B3f8489195d32a328 callsite= label=DeployImplementations
WARN [03-16|23:22:55.565] Revert                                   addr=0x551618101B3999B61c266b9B3f8489195d32a328 label=DeployImplementations err="execution reverted" revertMsg="unrecognized 4 byte signature: 201d2949" depth=1
WARN [03-16|23:22:55.565] Fault                                    addr=0x551618101B3999B61c266b9B3f8489195d32a328 label=DeployImplementations err="execution reverted" depth=1
WARN [03-16|23:22:55.565] callframe                                depth=1 byte4=0xfc4dcacb addr=0x551618101B3999B61c266b9B3f8489195d32a328 callsite= label=DeployImplementations
WARN [03-16|23:22:55.565] Revert                                   addr=0x551618101B3999B61c266b9B3f8489195d32a328 label=DeployImplementations err="execution reverted" revertMsg="unrecognized 4 byte signature: 201d2949" depth=0
Application failed: error in pipeline stage apply: error deploying implementations: failed to run DeployImplementations script: revert: unrecognized 4 byte signature: 201d2949

[jsvisa]

Sorry to hear that :) maybe the unrecognized 4 byte signature maybe not fully fixed

[opfocus]

https://github.com/ethereum-optimism/optimism/blob/op-deployer/v0.0.13/op-deployer/pkg/deployer/artifacts/locator.go

This seems to indicate support for files,
The problem may be that the apply command is not applicable

[opfocus]

If there is an acceptable answer, please mark it as the answer (you can also mark your answer as the answer).
If you still have problems please add a comment
If you have other questions, please open a new discussion.
We are considering closing this issue

[seromenho]

I don’t believe there’s a viable solution at the moment, or rather, I don’t think it’s currently possible. I suggest we go ahead and close the issue. Thank you for your time and input.