Why this matters now: Complements #2/#20 — without a stress test, the financial-safety fixes cannot be proven or kept safe.
Problem / What: No load/soak test exists that hammers proof approval + reward payout with process restarts and forced shutdowns to detect duplicate on-chain payments or duplicate RewardPayout rows.
Key Challenges: Driving enough throughput with controllable failure injection (kill worker mid-payout, drop Redis, drop Postgres) and asserting global invariants (one txHash per proofId, sum of payouts == sum of approved rewards).
Acceptance Criteria:
- A soak test in CI (or a documented manual harness) asserts zero duplicate payouts across injected failures.
- Invariants are checked by a query, not by manual inspection.
Relevant files/functions: tests/integration/proof-to-reward.test.ts, src/workers/rewardWorker.ts, src/services/rewardPayoutSweeper.ts.
Out of scope: Full chaos-engineering platform.
Labels: advanced, testing, reliability, security
Why this matters now: Complements #2/#20 — without a stress test, the financial-safety fixes cannot be proven or kept safe.
Problem / What: No load/soak test exists that hammers proof approval + reward payout with process restarts and forced shutdowns to detect duplicate on-chain payments or duplicate
RewardPayoutrows.Key Challenges: Driving enough throughput with controllable failure injection (kill worker mid-payout, drop Redis, drop Postgres) and asserting global invariants (one
txHashperproofId, sum of payouts == sum of approved rewards).Acceptance Criteria:
Relevant files/functions:
tests/integration/proof-to-reward.test.ts,src/workers/rewardWorker.ts,src/services/rewardPayoutSweeper.ts.Out of scope: Full chaos-engineering platform.
Labels: advanced, testing, reliability, security