End of a chapter.
My time at QuillAudits has come to an end.
Grateful for the experience. I learned a lot and worked with an amazing team.
During this time, I:
- Completed over 14+ audits, uncovering multiple H/M/L issues
- Contributed to Quillshield AI. My work was crucial for the modification of V2 and laid the foundation for V3
- Found key edge cases across several products released at the time eg. Wachai, TokenSense, Quillcheck etc
Been having a lot of questions about road map and how to learn web3 security.
On this thread I’ll be sharing every resource I have used. I’ll simplify it so you’d work with it in steps.
Follow the roadmap sequentially don’t skip any course!
#1
It's been a hell of a year.
Took sometime off hunting to learn various languages go, move and c++.
Studied DLT systems, crosschain bridges etc.
Restarting hunting with these arsenals.
Seen a lot of success stories... Its time to make mine
Will update here in 3 months
@beatsieboyz - Basically articles
- Docs of the protocol
- Analyzed the commit before audits
- Studied the reports
For those that have been hacked. Studied the hacks and reproduce locally
Or that contests remain the most effective form of audit when it comes to finding more bugs faster per dollar than any other method.
@zellic_io should open source the @code4rena platform and operational manual so projects or foundations or VCs or @ethereum or @_SEAL_Org can run these as I always felt they were: public goods. cc @samczsun
Lots of bridge hacks happening.
If you own a bridge it’s time to re-audit those contracts properly again.
This is beyond asking audit firms to check if the bug in hacked contract A is in your own code.
@0xCharlesWang@sockdrawermoney@zellic_io@code4rena@ethereum@_SEAL_Org Love firms that do this
Run a contest on some of your audited contracts and be shocked on the number of issues that would be found.
Take into consideration that contest bug severity is way different from private audits