ethernaut VS hardhat-template

- https://github.com/OpenZeppelin/ethernaut - do ALL the security oriented exercises

View on GitHub

In the following code snippet, we have 4 contracts: Sender, SenderWithRequire, SenderWithEmit and Receiver. Here, Receiver will play the King contract role.

You could contribute to Ethernaut, such as updating to Solidity 0.8: https://github.com/OpenZeppelin/ethernaut

It seems like every single week, I see things about Foundry. As someone that has been using a fairly standard Hardhat template for my projects the past year, I feel like this gets the job done, but I am wondering what I am missing?

To help getting started easier I am looking into some boilerplate starter kits such as https://github.com/paulrberg/solidity-template etc. Basic question, but what is the best practice in terms of organizing your smart contract dev stuff such as .sol files, hardhat, solhint, solcover, etc. with your front-end (website) dApp code? Do you keep everything in one repository? Do you keep them separated? The front-end part (let's say Sveltekit for example) and ethers.js need the ABI json right? When you deploy your front-end website and are keeping everything in one repo, should you exclude your contract files from the build? I suppose the JS framework will already exclude folders like /contracts that are in the root from the build.

I also really like this template for a web3+React website with a simple connect button: https://github.com/PaulRBerg/solidity-template

..and if you are looking for a general toolchain I really love the starter template here: https://github.com/PaulRBerg/solidity-template