Skip to content
Drainproof
Demo mode. These reports are fixtures generated by running the Drainproof CLI against the bundled example policies. They are not results from your project.

← Run run_28b022e2

One smallest unit above the maximum is blocked: expected BLOCK, observed REQUIRE_APPROVAL

2026-11-06 20:03 UTC · finding run_28b022e2065846bea33b28014514a629:tx-limit-one-unit-above-maximum

critical

Problem

25.000001 USDC is one atomic unit above max_transaction_amount and must be blocked.

Observed behaviour was more permissive than expected; severity is the scenario's declared risk (critical).

Remediation

Do not use floating-point comparison or rounding for limits. Convert amounts to integer atomic units and keep max_transaction_amount at the intended value.

Expected behaviour

{"decision":"BLOCK","reason_codes":["AMOUNT_EXCEEDS_TRANSACTION_LIMIT"],"reason_codes_exact":false,"absent_reason_codes":[]}

Observed behaviour

{"decision":"REQUIRE_APPROVAL","reason_codes":["APPROVAL_REQUIRED_AMOUNT"],"replay":false}

Reproduce

  1. drainproof test --scenario tx-limit-one-unit-above-maximum
  2. Scenario file: ../../packages/cli/templates/scenarios/transaction-limits/tx-limit-one-unit-above-maximum.yaml (step 1 of 1: propose)

Evidence: ../../packages/cli/templates/scenarios/transaction-limits/tx-limit-one-unit-above-maximum.yaml, step 1 · definition sha256:beba85b3e50b… · policy sha256:e9871ec1fde6…

Scenario steps

  1. #1proposefailedexpected BLOCK, observed REQUIRE_APPROVAL
    Expected
    {
      "decision": "BLOCK",
      "reason_codes": [
        "AMOUNT_EXCEEDS_TRANSACTION_LIMIT"
      ],
      "reason_codes_exact": false,
      "absent_reason_codes": []
    }
    Observed
    {
      "decision": "REQUIRE_APPROVAL",
      "reason_codes": [
        "APPROVAL_REQUIRED_AMOUNT"
      ],
      "replay": false
    }