dos-griefing-analysis

Identify and document DoS and griefing vulnerabilities in smart contracts.

117|24|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/quillai-network/qs_skills --skill dos-griefing-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dos-griefing-analysis
Source: https://github.com/quillai-network/qs_skills/tree/main/plugins/dos-griefing-analysis/skills/dos-griefing-analysis
Command: npx skills add https://github.com/quillai-network/qs_skills --skill dos-griefing-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and documents DoS and griefing vulnerabilities in smart contracts, enabling auditors to proactively harden systems and preserve availability.

Core Features & Use Cases

  • Unbounded Loop DoS detection: identify loops whose bounds grow with usage and propose safe pagination or pull patterns.
  • External Call DoS mitigation: detect batch operations where a single failed external call blocks all processing and recommend try/catch or per-item handling.
  • Gas/63-64 griefing awareness: flag meta-transaction and relayer patterns that forward insufficient gas or fail conditionally, with guardrails.
  • Storage growth controls: highlight storage growth that makes iterations expensive and suggest limits or paginated models.
  • Cooldowns and timestamps: identify griefing via timestamp resets that can block valuable actions and propose internal accounting.
  • Force-fed ETH and balance-invariant issues: warn on self-destruct or balance-based checks and encourage internal accounting.

Quick Start

Run a DoS and griefing audit on a target contract to map common patterns and generate mitigations.

Frequently Asked Questions about dos-griefing-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a griefing vulnerability in Ethereum smart contracts?

A griefing vulnerability in Ethereum occurs when an attacker causes operational blockage or financial loss to a victim at little cost, exploiting external calls, batch operations, or gas forwarding patterns.

How do I detect unbounded loop DoS vulnerabilities in Solidity?

Detect unbounded loop DoS vulnerabilities in Solidity by identifying loops whose iteration bounds grow with usage, then applying safe pagination or pull payment patterns to prevent out-of-gas failures.

How does the 63/64 gas griefing attack work in smart contracts?

The 63/64 gas griefing attack exploits the EIP-150 gas forwarding rule in smart contracts by providing insufficient gas to subcalls, causing conditional failures that block meta-transaction relayers.

Can I audit force-fed ETH and balance-invariant issues in smart contracts?

Yes, you can audit force-fed ETH and balance-invariant issues by detecting contracts that rely on exact address balances, warning against self-destruct injections, and enforcing internal accounting.

What are the limitations of using timestamps for cooldowns in smart contracts?

Using timestamps for cooldowns in smart contracts risks griefing via block timestamp manipulation, which can indefinitely delay valuable actions and requires internal accounting mechanisms instead.

How do I prevent external call DoS in batch operations?

Prevent external call DoS in batch operations by implementing try/catch blocks or per-item error handling so a single failed external call does not block all subsequent processing.