This repository was archived by the owner on Jan 9, 2025. It is now read-only.
feat: deploy account from zero #1065
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
enitrat
commented
Apr 3, 2024
enitrat
force-pushed
the
feat/account-deploy-from-zero
branch
from
acf0c28 to
a51faaa
Compare
enitrat
commented
Apr 4, 2024
enitrat
force-pushed
the
feat/account-deploy-from-zero
branch
2 times, most recently
from
c4e268c to
8551b43
Compare
|
@ClementWalter once I have your greenlight I adapt the EF-Test runner accordingly, and then we can merge everything docs are in #1056 |
enitrat
force-pushed
the
feat/account-deploy-from-zero
branch
from
a89c8a3 to
2e51632
Compare
This was referenced Apr 11, 2024
Merged
matthieuauger
pushed a commit
to matthieuauger/kakarot
that referenced
this pull request
Nov 9, 2024
* bump reth to v0.2.0-beta.7 * fix comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Time spent on this PR: 0.3d
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Resolves #1064 Resolves #1046
What is the new behavior?
This change is