Content
@
https://opensea.io/collection/evm-6
0 reply
0 recast
2 reactions
Emmanuel🦉⌐◨-◨🎩🍥
@emmanuel
whenever i see a major dapp use reentrancy guards in their contracts instead of being strict about their invariants, a part of me chuckles a bit.
0 reply
0 recast
2 reactions
Weso
@weso
Well it's because reentrancy is a real problem and I've seen dapps remove them (because they they think they could) and get hit before.
0 reply
0 recast
0 reaction
Karenmaxi
@karenmaxi
True but your forgetting that if Protocols implement the checks and effects pattern then there is no reentrancy risk.Protocols using Reentrant modifiers can still get attacked by cross contract reentrancy and sometimes cross function reentrancy.
0 reply
0 recast
0 reaction
Weso
@weso
You assume every web3 developer can make no mistake. Immutability is a big reason to have a stop gap in place. Everyone makes mistakes.
0 reply
0 recast
0 reaction
Karenmaxi
@karenmaxi
I never said they can't make mistakes but a good engineer will know these risks.For the 5000 fork lending protocols ya your right they should spend the extra gas.Again the issue is an external call that doesn't reflect the internal state.
0 reply
0 recast
0 reaction
