My Smart Contract Audit Process (Part 2)

How to Become a Smart Contract Auditor: jacksonkelley....
In this video, I do the second pass of my smart contract audit process. We check for re-entrancy, signature replays, and find some accounting errors in this video. The first pass can be found in this video:
• My Smart Contract Audi...
At the end I talk about my Gumroad "How to Become a Smart Contract Auditor" document:
Smart contract auditors are in high demand. This means they're being paid handsomely for their skills, charging anywhere from $100-1000+ per hour. 🤯 They can also work from anywhere in the world, or if they choose, without a boss. 😎
Why are these hackers paid so well? Because there aren't many of them. So, why aren't more people doing this? Because resources for learning how to do it are not easy to find. What are you going to do, Google "how to become a smart contract auditor"? Good luck.
Even if you aren't interested in becoming an auditor, nearly all Solidity developer interviews focus on security. You will get rejected from Solidity positions if you don't understand security.
I've compiled a list of resources that I personally used to become a smart contract auditor. With this list, you'll have a clear path from A-Z to become a smart contract auditor yourself. From Solidity basics, all the way to landing your first job, and keeping up to date with the latest multi-million dollar smart contract hacks. Worried you won't be good enough to land a job after this? I'll personally hire you if you're unable to find a position at the firms listed in the resources.
Auditing firms are charging over $2500 for this content, and only accepting 100 students, but I'm giving it to you for only $100, which you'll make within your first hour of work as an auditor. Worried you might not like what you get? There's also a money-back guarantee. The only prerequisite is that you have a basic understanding of programming.
So, what are you waiting for? Let's get hacking! 👨🏻‍💻
How to Become a Smart Contract Auditor: jacksonkelley....

[@andyli]

really good points about writing out a POC

[@jacksonk]

Thinking back on it, I would almost call it more like "exploratory hacking" or something because often I'm not even sure there's an exploit, but it gives me a deeper understanding of the code and helps me brainstorm other potential attacks.

[@steiner254]

Interesting

[@farruhsydykov8420]

Thanks a lot, man!

[@computerevolve8416]

making videos like this thanks jackson

[@rodrigota7432]

thanks, sir Where can I find C Michel's talk on y academy?

[@jacksonk]

It's hosted here: drive.google.com/drive/folders/1-hQPcokzWxd5fz3hdUKxAZmyaBRAPRFL not sure if it's publicly accessible or not though.