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

Both Cairo0 and Cairo1 accounts should always be predeclared #373

Closed
FabijanC opened this issue Mar 6, 2024 · 0 comments · Fixed by #402
Closed

Both Cairo0 and Cairo1 accounts should always be predeclared #373

FabijanC opened this issue Mar 6, 2024 · 0 comments · Fixed by #402
Assignees
Labels
enhancement New feature or request

Comments

@FabijanC
Copy link
Contributor

FabijanC commented Mar 6, 2024

As noted in this Discord thread, when users select --account-class cairo0, only cairo0 is predeclared. When they select --account-class cairo1, both cairo0 and cairo1 are predeclared. This happens because we predeploy the not-for-public-use chargeable account (used in tests), which always uses cairo0 implementation.

Why this could be useful? Users might want to predeploy cairo0 accounts, but later on be able to deploy cairo1 accounts, or vice versa.

Related: #171

@FabijanC FabijanC added the enhancement New feature or request label Mar 6, 2024
@mikiw mikiw self-assigned this Mar 6, 2024
@mikiw mikiw added the OnlyDust label Mar 6, 2024
@mikiw mikiw removed their assignment Mar 19, 2024
@FabijanC FabijanC self-assigned this Mar 28, 2024
@FabijanC FabijanC removed the OnlyDust label Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants