Deposit Capacity Attacks

Abierto
#283 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@mts1715 ya está trabajando en esto.

Desde el 24/3/2026.

  • #299 de @mts1715 — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Context

Current Gap: Tests cover normal usage, need adversarial scenarios.

Missing Test Coverage:

  • Griefing Attacks

    • Attacker creates 1000 positions
    • Each position deposits minimum amount
    • Total consumes all deposit capacity
    • Legitimate users cannot deposit
  • Front-Running Capacity

    • User A prepares large deposit transaction
    • Attacker sees pending transaction
    • Attacker front-runs and consumes capacity
    • User A transaction fails due to insufficient capacity
  • Per-User Limit Bypass

    • User limit = 5% of capacity
    • User creates multiple accounts
    • Each account deposits up to limit
    • Effectively bypasses individual limit (Sybil attack)
  • Capacity Regeneration Manipulation

    • Attacker monitors regeneration timing
    • Submits deposits immediately after regeneration
    • Monopolizes regenerated capacity
    • Legitimate users starved
  • Queued Deposit Exploitation

    • User deposits exceed per-deposit limit
    • Excess queued for async processing
    • User cancels queued deposits after manipulating state
    • Potential for race conditions

Recommended Tests:

Test: Create 100 positions, each deposits 1% of capacity
Test: Front-run large deposit, consume capacity first
Test: User A creates 20 accounts, bypasses per-user limit
Test: Attacker deposits immediately after each regeneration cycle
Test: Queue large deposit, attempt to exploit during async processing
Lenguaje dominante
Cadence
Estrellas
40
Forks
2
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de onflow/FlowALP

Todos los issues de onflow/FlowALP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.