Skip to content
Discussion options

You must be logged in to vote

Seems it's a op-deployer's bug, currently if you want to deploy with op-deployer, could you plase try op-deployer/v0.0.10 instead of the latest develop branch. And with the below contracts:

l1ContractsLocator = "tag://op-contracts/v1.6.0"
l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts"

This is a test tx to deploy the chains https://sepolia.etherscan.io/tx/0x642926f6e1535f242e070b2e2b033895870e21bf81659a2b3e47a0c655d1bbb5

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
3 replies
@jsvisa
Comment options

Answer selected by Guan21
@Guan21
Comment options

@jsvisa
Comment options

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
op-stack-deployment Questions relating to deploying your own OP Stack. discussion-metrics Used by Github Action to gather discussion metrics on the question and answer section.
2 participants