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

Faucet setup for funding test accounts #11765

Closed
Tracked by #9456
spypsy opened this issue Feb 5, 2025 · 0 comments · Fixed by #12076
Closed
Tracked by #9456

Faucet setup for funding test accounts #11765

spypsy opened this issue Feb 5, 2025 · 0 comments · Fixed by #12076
Assignees

Comments

@spypsy
Copy link
Member

spypsy commented Feb 5, 2025

we currently have a lot of accounts funded from a mnemonic that will need to be assigned for each task we run on Sepolia (e.g. accounts 1-50 for zombie chain, 51-54 for e2e test etc)
this isn't very manageable if we want to start running multiple tests at the same time, especially now that e2e test is part of CI.
Need a setup where a main Sepolia account acts as faucet and then funds accounts according to needs, using mnemonic.

e.g. for e2e test:

  1. Create new mnemonic
  2. Take 5 first accounts derived from it
  • 3 validators
  • 1 contract deployer
  • 1 prover
  1. Run test
  2. Refund main account
@spypsy spypsy self-assigned this Feb 5, 2025
spypsy added a commit that referenced this issue Feb 26, 2025
Fixes #11765 
Updating how we make sepolia deployments on k8s. 
Instead of fixed pre-funded addresses, we have a single private key that
funds new addresses for each new deployment.
Also fixes setting up the transaction bot for sepolia deployments
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 a pull request may close this issue.

1 participant