Reentrancy is a problem as old as solidity. The most infamous hack in Ethereum (the Dao Hack) triggered a lot of discussion on the subject back in 2016. But is it still relevant. Just last year the Burgerswap hack, SurgeBNB hack, and Cream Hack, all had a reentrancy exploit component.
In this video we evaluate the causes of reentrancy, we create our own contract with a reentrancy vulnerability so we can exploit it, and then we fixed it from three different paradigms.
00:00 - 02:14 Intro
02:14 - 14:17 The vulnerability
14:17 - 25:07 Exploiting the vulnerability
25:07 - 29:12 Creating a testing dashboard
29:12 - 30:17 Creating an innocent user contract
30:17 - 37:53 Fixing using especial transfer()
37:53 - 44:33 Fixing with check and effects pattern (best practice)
44:33 - 51:50 Fixing with non-reentrant modifier (mutex pattern)
🔨💻 GitHub repository at:
https://github.com/DanielMoralisSampl...
🔨💻 Forum for posting questions:
https://forum.moralis.io/t/smart-cont...
🔨💻 START USING MORALIS:
https://moralis.io/?utm_source=youtub...
💬 Join Our Discord: https://moralis.io/mage?utm_source=yo...
📃 Moralis Docs: https://docs.moralis.io/
😎 Merch: https://merch.moralis.io
🐦 Twitter: / moralisweb3
🤖 Reddit: / moralisweb3
🔔 Subscribe to all notifications: / @moralisweb3
🎓 Moralis Academy: https://academy.moralis.io/?utm_sourc...
#moralis #ivanontech
ethereum programming, ethereum developer, dapps, ethereum smart contracts, blockchain programming, ethereum dapp build, create a coin, ethereum coding, ethereum development, polkadot programming, cardano programming, moralis, web3, web3 programming, blockchain coding, blockchain for programmers, blockchain archive node, blockchain nodes