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.

Sign up for GitHub

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

Jump to bottom

era-test-node integration #677

Closed
Karrq opened this issue Oct 29, 2024 · 2 comments
Closed

era-test-node integration #677

Karrq opened this issue Oct 29, 2024 · 2 comments
Labels
challenging 🏴‍☠️ Indicates a difficult item needs more info ℹ️ Item requires more detail needs triage ♟️ Issue needs to be picked up or assigned p3 🔵 Indicates low priority item upstream-parity 🟰 Needed for upstream feature parity

Comments

@Karrq
Copy link
Contributor

Karrq commented Oct 29, 2024

Foundry only supports anvil as a local node which does not work entirely for zkSync.

  • era-test-node integration: This would be ideal for zkSync specific local development.

Work on integrating era-test-node in a way similar to how Anvil is currently utilized, enhancing the testing infrastructure.

Extend the zksyncNode functionality that is found in the test-helpers.
@Karrq Karrq added challenging 🏴‍☠️ Indicates a difficult item needs more info ℹ️ Item requires more detail p3 🔵 Indicates low priority item needs triage ♟️ Issue needs to be picked up or assigned upstream-parity 🟰 Needed for upstream feature parity labels Oct 29, 2024
@dutterbutter
Copy link
Collaborator

Some additional info here:

We intend to rebrand era-test-node to anvil-zksync, and include in the foundryup-zksync installation script for dev convenience. Work in progress right now:

  • API completeness, including anvil namespace
  • CLI parity with anvil for dev convenience

@dutterbutter
Copy link
Collaborator

Closing as we have included in installation process in #765 which is the extent of this integration atm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
challenging 🏴‍☠️ Indicates a difficult item needs more info ℹ️ Item requires more detail needs triage ♟️ Issue needs to be picked up or assigned p3 🔵 Indicates low priority item upstream-parity 🟰 Needed for upstream feature parity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Karrq @dutterbutter