Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to find L1 contract addresses #84

Open
zhouop0 opened this issue Oct 10, 2024 · 4 comments
Open

How to find L1 contract addresses #84

zhouop0 opened this issue Oct 10, 2024 · 4 comments

Comments

@zhouop0
Copy link

zhouop0 commented Oct 10, 2024

Like title. I want to launch L1 and L2 to experiment dispute game. In old version, I can see contract addresses which about dispute game on console logs, like disputegameproxy.sol, faultdisputegame.sol and so on, but new version I can not find them. In this new version, How to find L1 contract addresses?

@0xalex88
Copy link

The only way I've found is to docker exec into the op-node container and cat /network-configs/rollup-* to print the system address, from there you can use the storage slots and get the other addresses. There are also other files where you can get the implementations addresses but I didn't find one that has all the proxies

@tynes
Copy link

tynes commented Dec 9, 2024

It would be ideal if op-deployer could print this to stdout cc @mslipper

@tynes
Copy link

tynes commented Jan 13, 2025

I believe @sigma has made progress on this

@sigma
Copy link
Collaborator

sigma commented Jan 13, 2025

So long story short, those addresses are contained in the op-deployer artifact in kurtosis (named op-deployer-configs)
Inside that artifact, look at the state.json file

https://github.com/ethereum-optimism/optimism/blob/develop/kurtosis-devnet/pkg/kurtosis/sources/deployer/cmd/main.go is a tiny helper to dump some of the information contained in there (including the addresses you mention)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants