Revert Bombs & Refund Traps: Gas Griefing in the Wild
You've optimized your contract to the bone. Storage packed, loops unrolled, calls batched. Then someone sends a transaction that reverts at the last s...
6 articles in this category
You've optimized your contract to the bone. Storage packed, loops unrolled, calls batched. Then someone sends a transaction that reverts at the last s...
You've just deployed a shiny new Solidity contract. Gas overheads are low, users are happy. Then someone sends a tiny amount of ETH with calldata, and...
You've done it. You packed your struct like a Tetris pro, squeezing 10 uint64s into one slot, patting yourself on the back for saving 5,000 gas per tr...
So your loop is burning gas like a rocket launch. You've watched the estimator spit out numbers that make your eyes water. Before you start ripping ou...
You're looking at a contract that's borderline on gas. A few optimizations could save users real money. But two shortcuts in particular—switching to l...
You've just shaved 200 gas off a swap function. Feels good, right? But what if that 'optimization' silently corrupts your contract's storage layout, m...