Tired of typing long commands and environment variables? Let's simplify our workflow using a .env file! Boost your productivity and focus on building. 🧵👇

Step 1: Create a .env File

In your project directory, create a .env file to store your environment variables. 🗂️

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

Step 2: Add Environment Variables

Populate your .env file with variables that will make your life easier. Here are some that we'll add for our future work (replace with your actual values 🔑).

⚠️ Important Security Reminder

Before proceeding, a quick reminder of “The .ENV Pledge” from @patrickalphac ’s @cyfrin courses, to always use test accounts with no real assets when developing. Safety first! 🔒

⚠️ Important Security Reminder

Before proceeding, a quick reminder of “The .ENV Pledge” from @patrickalphac ’s @cyfrin courses, to always use test accounts with no real assets when developing. Safety first! 🔒 https://github.com/Cyfrin/foundry-full-course-cu/discussions/5

⚠️ Important Security Reminder

Before proceeding, a quick reminder of “The .ENV Pledge” from @patrickalphac’s @cyfrin courses, to always use test accounts with no real assets when developing. Safety first! 🔒

⚠️ Important Security Reminder

Before proceeding, a quick reminder of “The .ENV Pledge” from @patrickalphac’s @cyfrin courses, to always use test accounts with no real assets when developing. Safety first! 🔒 https://github.com/Cyfrin/foundry-full-course-cu/discussions/5

Step 3: Load the Variables

In your terminal, load the variables so tools like cast will automatically use these variables. No more repetitive typing! 🎯

Step 4: Verify the Variables

Ensure the variables are loaded correctly by echoing one of them. You should see http://localhost:8011 printed in your terminal. Success! ✅

zkSync

With your environment set up, you're ready to interact seamlessly with your local /zksync Era fork. Next, we'll explore checking balances using cast call. Stay tuned! 🔍