docs
hardhat-template
Our great sponsors
| docs | hardhat-template | |
|---|---|---|
| 5 | 5 | |
| 156 | 1,919 | |
| 1.3% | - | |
| 9.2 | 6.8 | |
| 5 days ago | about 2 months ago | |
| JavaScript | TypeScript | |
| Creative Commons Zero v1.0 Universal | 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.
docs
-
If you had money and power at your disposal, how would you spend your time?
Also I know it may be too much but if it is really your things check out the technical documents: https://docs.stacks.co/ and https://docs.hiro.so/intro
-
"'You have no idea what you’re doing with your money if you’re not investing in crypto,' is an actual thing said to me by a finance bro once."
In addition, if it is more your thing honestly check out a lot of the more technical information on smart contracts,dApps and stacks itself from Hiro https://docs.hiro.so/intro and Stacks https://docs.stacks.co/
- This is not a meme.
- Web3.0 Resources
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?
sypool - Sypool is a custodial STX mining pool using smart contracts on the Stacks blockchain for trustless contributions & reward redemption. 🏊 ♾️
prb-math - Solidity library for advanced fixed-point math
ZeroNet - ZeroNet - Decentralized websites using Bitcoin crypto and BitTorrent network
hardhat-gas-reporter - Gas Usage Analytics for Hardhat
ethernaut - Web3/Solidity based wargame
uniswap-v3-token-swap - example code of uniswapV3 token swaps with hardhat and ethersjs
smart-contract-best-practices - A guide to smart contract security best practices
multicall-batcher - multicall with ease
full-blockchain-solidity-course-py - Ultimate Solidity, Blockchain, and Smart Contract - Beginner to Expert Full Course | Python Edition
web3-react - A simple, maximally extensible, dependency minimized framework for building modern Ethereum dApps
useDApp - Framework for rapid Dapp development. Simple. Robust. Extendable. Testable
foundry-lsp-smart-contracts - Repo used only for testing.