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

Or 1440 resolved devnet issue #94

Merged
merged 4 commits into from
Mar 18, 2024
Merged

Conversation

ohbyeongmin
Copy link
Collaborator

You can specify the admin account. the admin account you want to set must match the account entered in the devnet config file.
If you don't set the environment variable, it works exactly as before.

Basic admin account(in devnetL1-template.json):
address : 0xa0Ee7A142d267C1f36714E4a8F75612F20a79720
private key : 0x2a871d0798f97d79848a013d4936a73bf4cc922c825d33c1cf7073dff6d409c6

Usage:

export DEVNET_ADMIN_PRIVATE_KEY=0x2a871d0798f97d79848a013d4936a73bf4cc922c825d33c1cf7073dff6d409c6

make devnet-up

# If you unset it, the contract will be deployed to a random account in geth devmode as before.
unset DEVNET_ADMIN_PRIVATE_KEY

When to use?

  • Use it when you need to do something with the admin account on devnet.
  • For example, when testing an L1 contract upgrade, you can use

@steven94kr
Copy link
Member

Is it needed to change geth version? 🙇🏼‍♂️

@ohbyeongmin
Copy link
Collaborator Author

ohbyeongmin commented Mar 15, 2024

Yes there was an error in the previous geth version. it have a problem when applying custom genesis(for change chainId).

In monorepo, geth is only used to extract allocs to create the genesis file for devnet L1, so I don't think the version change will cause problems elsewhere.

Let me know if I missed anything.

Copy link
Member

@steven94kr steven94kr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much! 😍

@ohbyeongmin ohbyeongmin merged commit 2b68be3 into main Mar 18, 2024
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

Successfully merging this pull request may close these issues.

2 participants