"Often you will be working with code that has been audited by world-class security experts and put through extensive testing. That does not mean that there are no bugs, though — an audit is no guarantee for security and the list of audited projects which

"I think most of the time when developers are new to crypto and have a hard time learning Solidity, it is not due to the complexity of the language itself, but rather many skip learning about the fundamental inner workings of a blockchain... and try to approach writing a smart contract as you would write traditional software, which ends in confusion.

Should you find yourself in this position, ask yourself some questions of this type:

• who executes smart contract code?
• when is a smart contract executed?
• where is a smart contract’s data (storage) stored?
• why can a smart contract not call an API?

If you can reason about these questions with reasonable technical depth and nuance, you are ready for a deep dive into Solidity."

"I think when it comes to bug bounty hunting many people struggle with the question “where do I start, when do I end?” when examining a project.

The approach which works best for me is to set myself the goal of fully understanding the system to the point where I could reimplement it from scratch without being allowed a look at the original codebase.

Not from remembering the code, but from having understood what the application is supposed to do. If you have examined a project that far and have not found a bug, the chances of finding one by continuing is low. However, if there is a bug in there, your chances of finding it with this method are high."

For more insights into the mind of a crypto whitehat hacker and legendary bug bounty hunter, check Alex's (CTO of Ideamarket) interview below:

Interview with Legendary Bug Bounty Hunter Alexander Schlindwein