remix-ide
hardhat-template
Our great sponsors
| remix-ide | hardhat-template | |
|---|---|---|
| 3 | 5 | |
| 2,224 | 1,915 | |
| 0.7% | - | |
| 9.1 | 6.8 | |
| 8 days ago | about 1 month ago | |
| TypeScript | ||
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
remix-ide
- How does Remix write tests?
-
Web3.0 Resources
https://github.com/ethereum/remix-ide Solidity
-
# Learn: Solidity’s Smart Contract 🤝🏼 by Creating a Will📜!
One of the most common IDE for writing smart contracts is the remix IDE hosted on ethereum.org. This is the fastest way to get started with writing Smart contracts with solidity. It comes with all you need, a web browser-based compiler and about 15 free Ethereum account loaded with 100eth coin. These coins are on the Testnet not the Mainnet so don't even think of spending them🙄.
hardhat-template
-
Foundry vs. Hardhat template?
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?
-
Basic beginner questions concerning smart contracts and dApp front-end code organization
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.
- Web3.0 Resources
-
Confused by Web3 and best practices
I also really like this template for a web3+React website with a simple connect button: https://github.com/PaulRBerg/solidity-template
-
I feel lost. (New Dev)
..and if you are looking for a general toolchain I really love the starter template here: https://github.com/PaulRBerg/solidity-template
What are some alternatives?
hardhat - Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software.
prb-math - Solidity library for advanced fixed-point math
truffle - :warning: The Truffle Suite is being sunset. For information on ongoing support, migration options and FAQs, visit the Consensys blog. Thank you for all the support over the years.
hardhat-gas-reporter - Gas Usage Analytics for Hardhat
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.
uniswap-v3-token-swap - example code of uniswapV3 token swaps with hardhat and ethersjs
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
smart-contract-best-practices - A guide to smart contract security best practices
bytecode-verifier - Compile Solidity source code and verify its bytecode matches the blockchain
multicall-batcher - multicall with ease
evm-opcodes - Ethereum opcodes and instruction reference
full-blockchain-solidity-course-py - Ultimate Solidity, Blockchain, and Smart Contract - Beginner to Expert Full Course | Python Edition