Ever wondered how to tinker with ZKsync mainnet locally? Turns out you can fork it using era_test_node and interact with contracts via Foundry! Today I learned, and soon you will too. Let’s dive into the journey! 🧵👇

I'm a little teapot who didn't fill out my bio

1️⃣ Setting Up the Playground

First things first, I’ll guide you through setting up era_test_node, forking the ZKsync mainnet, and configuring Foundry. It’s simpler than it sounds, and unlocks a world of local development possibilities! 🛠️

3️⃣ Checking Balances with Cast

We’ll use cast call from Foundry to check balances and call contract functions. Say goodbye to GUIs and hello to efficient CLI commands. 💻

4️⃣ Acquiring WETH on the Fork

Need some WETH to play around with? I’ll walk you through obtaining WETH on your local forked network. It’s essential for testing swaps and other interactions. 💰

5️⃣ Transferring WETH Made Easy

Next up, transferring WETH between accounts. Whether you’re simulating user interactions or testing contracts, transferring tokens is a fundamental skill. Let’s get those funds moving! 🔄

6️⃣ Swapping WETH on @uniswap

Finally, the big moment: swapping WETH on Uniswap using Foundry! We’ll execute swaps on our forked network, bringing everything together in a practical example. It’s trading, but in your own sandbox. 🛝

6️⃣ Swapping WETH on @uniswap 

Finally, the big moment: swapping WETH on Uniswap using Foundry! We’ll execute swaps on our forked network, bringing everything together in a practical example. It’s trading, but in your own sandbox. 🛝

Stay Tuned!

I’ll be releasing threads on each of these steps soon and end it with adding to code.zksync.io. Whether you’re a seasoned dev or just curious, there’s something here for you. Let’s build and learn together! 🌐

2️⃣ Streamlining with .env Shortcuts

Let’s make life easier! I’ll show you how to use .env files to manage environment variables. No more copying and pasting addresses or private keys—just smooth sailing from here. ⛵