Griefing attacks in smart contracts involve non-financial disruption, exploiting logic flaws and gas negligence. Common patterns include timing resets, unchecked external calls, and block-spamming loops. Developers should implement safeguards like post-call checks, gas estimation, loop caps, and access controls. Detect griefing using static analysis tools and transaction monitoring. By preemptively addressing these issues, contracts become more robust against denial-of-service disruptions.
Q1: What is the main goal of a griefing attack?
A1: Disrupt contract operation
Q2: How does a griefing attacker disrupt a DelayedWithdrawal contract?
A2: Deposit minimal ETH to reset timer
Q3: Gas griefing occurs when:
A3: external calls fail due to insufficient gas
Q4: What is a practical method to prevent griefing?
A4: Check require(success) after external calls
