From c928878390eb8acc6a1eb861821dd086ca922b93 Mon Sep 17 00:00:00 2001 From: Dustin Brickwood Date: Thu, 28 Nov 2024 12:43:09 -0600 Subject: [PATCH] chore: fix readme --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8dc5836a..dd1d7a38 100644 --- a/README.md +++ b/README.md @@ -17,11 +17,15 @@ This crate provides an in-memory node that supports forking the state from other The goal of this crate is to offer a fast solution for integration testing, bootloader and system contract testing, and prototyping. -🔗 For a detailed walkthrough, refer to the [official documentation](https://docs.zksync.io/build/test-and-debug/in-memory-node). +🔗 **For a detailed walkthrough, refer to the following resources:** + +- [Official documentation: Anvil-ZKsync](https://docs.zksync.io/build/test-and-debug/in-memory-node) +- [Foundry Book: Anvil for zkSync](https://foundry-book.zksync.io/reference/anvil-zksync/) +- [Rust Book: Anvil-ZKsync](https://matter-labs.github.io/era-test-node/era_test_node/index.html) ## 📌 Overview -The In-Memory Node is designed for local testing and uses an in-memory database for storing state information. It also employs simplified hashmaps for tracking blocks and transactions. When in fork mode, it fetches missing storage data from a remote source if not available locally. Additionally, it uses the remote server (openchain) to resolve the ABI and topics to human-readable names. +`anvil-zksync` is designed for local testing and uses an in-memory database for storing state information. It also employs simplified hashmaps for tracking blocks and transactions. When in fork mode, it fetches missing storage data from a remote source if not available locally. Additionally, it uses the remote server (openchain) to resolve the ABI and topics to human-readable names. ## ⚠️ Caution