foundry VS subnet-evm

I realize that I want that change applied to all of my projects which use the same stack (e.g. all of my Solidity projects built with Foundry)

We scratched the surface of Foundry’s code in part 1. Let’s go a bit deeper and try to create a new cheatcode this time.

Also learning how to use one of these development environments instead of Remix is necessary: 1. Hardhat: https://hardhat.org 2. Foundry: https://github.com/foundry-rs/foundry

I just made my first (really small) contribution to Foundry (a toolkit to help develop smart contracts for Ethereum) today, and I really enjoyed it! 😍

Check out Foundry. It's faster and better than Hardhat IMO.

After you feel comfortable with this deployment flow, try deploying smart contracts on your chain with Remix, Hardhat, or Foundry. You can also experiment with customizing your Subnet by addingprecompiles or adjusting the airdrop.

Foundry

Forge: Ethereum testing framework (like Truffle, Hardhat, and DappTools).

Also check out foundry, definitely a different approach but doesn't use Javascript, you do most of your actions in solidity.

Since you can define your own VM, you can define whatever minting logic you want! You have complete control to create per block minting logic or otherwise to manipulate the EVM state however you see fit by creating a fork of Subnet-EVM. The simplest way to define some form of minting logic will be to set the Coinbase address that the Subnet-EVM will use such that all of the fees will be sent directly to that address allowing you to re-distribute these funds as you see fit.

Subnet-EVM APIs are identical to Coreth APIs, except Avalanche Specific APIs starting with avax. Subnet-EVM also supports standard Ethereum APIs as well. For more information about Coreth APIs see here.

Once you've developed a stable Subnet you like, see Create an EVM Subnet on Fuji Testnet to take your Subnet one step closer to production.

Familiarity with process of Deploying a Subnet on Testnet and Deploying a Permissioned Subnet on Mainnet

Avalanche is closing out the year strong with the final AvalancheGo release of 2022. Avalanche Warp Messaging (AWM) is rolling out in AvalancheGo Banff 5, bringing fast, reliable native communications to all Avalanche Subnets. AWM Is available today in both the Golang and Rust VM SDKs for use by any VM builder. Soon, this capability will be rolled out to the subnet-evm, giving Subnet creators native, cross-chain communication capabilities out-of-the-box.

To create an Ethereum Virtual Machine (EVM) compatible Subnet, Avalanche-CLI runs Subnet-EVM as its virtual machine.

After architecting your Subnet environment on the local machine, proving the design and testing it out on the testnet, eventually you will need to deploy your Subnet to production environment. Running a Subnet in production is much more involved than local and testnet deploys, as your Subnet will have to take care of real world usage, maintaining uptime, upgrades and all of that in a potentially adversarial environment. The purpose of this document is to point out a set of general considerations and propose potential solutions to them.

A Subnet and EVM blockchain has been created. Avalanche tools allow users to do this on Mainnet, Fuji or a Local network.

The Subnet-EVM is a simplified version of Coreth VM (C-Chain). This chain implements the Ethereum Virtual Machine and supports Solidity smart-contracts as well as most other Ethereum client functionality. It can be used to create your own fully Ethereum-compatible Subnet running on Avalanche. This means you can run your Ethereum-compatible dApps in custom Subnets, defining your own gas limits and fees, and deploying solidity smart-contracts while taking advantage of Avalanche's validator network, fast finality, consensus mechanism and other features. Essentially, think of it as your own Ethereum where you can concentrate on your business case rather than the infrastructure. See subnet-evm for further information.