Skip to content

[Execution] Detect transient liquidity manipulation around simulation and settlement #757

Description

@fishonamos

Problem

An attacker can distort shallow pools during simulation or just before execution, causing unsafe routes despite nominal slippage limits.

Required work

Add liquidity-depth, historical deviation, multi-source, and pre-settlement checks with configurable circuit breakers.

Acceptance criteria

  • Manipulation signals are recorded with the quote.
  • High-risk routes require stricter policy or rejection.
  • Checks cannot be bypassed by splitting a route.
  • Adversarial tests model flash liquidity and reserve spoofing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave program

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions