foundry VS solidity-template

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.

New updates to solidity-template are available! This template now supports more networks than ever. And for the first time, streamlined contract development to zk rollup L2s are possible!

Awesome to see a mention of solidity-template here! Check out the thread for more info.

This template includes an easy-to-follow example Counter.sol, with its interface ICounter.sol, Unit Test file Counter.t.sol, and Integration Test file counter.test.ts.

Reference for on-chain developers writing contracts that call these contracts in your Unit Test files to see the expected usage in Solidity.

solidity-template's sample contract, Counter.sol, is trivial, so the value add isn't observable here. Let me share a recent example where off-chain logic would never be able to be handled inside the Foundry unit tests: