Grinding Attack

Overview

A grinding attack exploits a system that lets participants try many candidate values before committing to one. By testing nonces, block contents, keys, timestamps, or commitments, an attacker selects the attempt producing the most favorable outcome.

Targets include leader election, validator selection, lotteries, proof-of-stake randomness, and protocol committees. Even a small per-attempt bias can become significant when an attacker has many trials, greater computation, or control over when information is revealed.

Defenses include unpredictable external entropy, verifiable random functions, commit-reveal schemes with penalties, limited attempts, and binding inputs before outcomes are known. Designers must analyze abort behavior because refusing unfavorable reveals can itself create selection power.

Grinding Attack is an attack or weakness pattern that repeatedly varies permitted inputs to bias a supposedly random selection, consensus outcome, committee assignment, or cryptographic result. Grinding turns optional input choices into hidden influence, so randomness designs must limit trials, aborts, and information available before commitment.

Assessment of Grinding Attack should trace an attack or weakness pattern that repeatedly varies permitted inputs to bias a supposedly random selection, consensus outcome, committee assignment, or cryptographic result from prerequisite and entry point through observable impact on the affected service. A theoretical weakness or scanner result involving attack, consensus outcome, and committee assignment should not be reported as exploitation without corroborating logs, transactions, or configuration evidence. Prevention, detection, containment, and recovery for the Grinding attack path should be tested against the architecture associated with attack, consensus outcome, and committee assignment.

Retesting for Grinding Attack should reproduce the Grinding attack path involving attack, consensus outcome, and committee assignment, examine adjacent paths, and verify the conditions for safely returning the affected service to normal operation.