-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content Suggestions #6
Comments
By all means if you'd be down to write a chapter / doc go for it! Do you have perhaps any favorite links for the above bulletpoints you mention (all of which are interesting IMO)? Your post on intro to Solidity dev is quite solid btw: https://jamesbachini.com/blockchain-developer/ |
moved to #8 |
Thank you. No I don't have any links, I was just brainstorming ideas for content rather than actually having resources for these. Shall I write a chapter on IDE's, something along the lines of when to use Remix vs Truffle vs Hardhat and talk about some plug-ins, testing and deployment scripts etc? I can submit it via a pull request in a week or so. |
Actually having read what you have so far it looks more focused on Hardhat so I'll write a chapter "Hardhat Plugins & Hacks" and get down some basic ideas which can be expanded on later. |
Some ideas for content:-
Recreating some famous hacks/bugs to demonstrate exploitable code and what to avoid
Reliable sources of libraries and audited code OpenZeppelin etc.
Design patterns
Quirks and gotchas with Solidity compiler
Hardhat vs Truffle
IDE Plugins and custom deployment scripts
How EVM works
Layer 2 technologies
Best practices for storing on chain vs off chain data
Gas optimisation tips
MEV and flashbots
Useful code snippets
Oracles and Uni twap
Swaps and UniV2 vs V3 concentrated liquidity
Connecting lego bricks to build yield farming vaults
Creating custom and bootlegged interfaces
Unit testing
Fuzzing and linters
Community Hackathons, Meetups, EthGlobal etc.
If you want any help I wouldn't mind researching and writing a chapter.
The text was updated successfully, but these errors were encountered: