idex-contracts-whistler
hardhat-template
Our great sponsors
| idex-contracts-whistler | hardhat-template | |
|---|---|---|
| 1 | 5 | |
| 43 | 1,919 | |
| - | - | |
| 0.0 | 6.8 | |
| over 1 year ago | about 2 months ago | |
| TypeScript | TypeScript | |
| GNU Lesser General Public License v3.0 only | 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.
idex-contracts-whistler
-
Tomochain stole 25k tomo (40-50k USD) from me while im dying of liver failure. I need this money to stay alive.
Whistler includes a wallet exit mechanism, which allows users to withdraw funds in the case IDEX is offline or maliciously censoring withdrawals. Calling exitWallet initiates the exit process, which prevents the wallet from subsequent deposits, trades, or normal withdrawals. Wallet exits are a two-step process as defined in controls.
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?
tribeca - A high frequency, market making cryptocurrency trading platform in node.js
prb-math - Solidity library for advanced fixed-point math
contracts - A set of reusable smart-contracts
hardhat-gas-reporter - Gas Usage Analytics for Hardhat
persssist - Storage decentralized application running on testnet for storing files metadata and IPFS protocol for uploading, sharing and downloading files of any kind.
uniswap-v3-token-swap - example code of uniswapV3 token swaps with hardhat and ethersjs
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.
smart-contract-best-practices - A guide to smart contract security best practices
defi-dapps-solidity-smart-contracts - This is a Web 3 Smart Contract learning and teaching repo which will be used to teach students all across Pakistan.
multicall-batcher - multicall with ease
WolfBot - Crypto currency trading bot written in TypeScript for NodeJS
full-blockchain-solidity-course-py - Ultimate Solidity, Blockchain, and Smart Contract - Beginner to Expert Full Course | Python Edition