Description: Build a test harness that deliberately fast-forwards ledger sequence/time mid-multi-step-flow (e.g. between listing and funding, or between funding and repayment) to verify no in-flight operation is silently corrupted by an entry expiring at an inopportune moment — directly stress-testing B40's TTL-resilience guarantees under adversarial timing rather than just at rest.
Context: B40 checks that individual entries survive to their expected expiry; this harness specifically targets the more subtle case of an entry expiring in the middle of a multi-transaction user flow, which is a distinct and easily-missed failure mode.
Scope & Acceptance Criteria: Test scenarios injecting a TTL-boundary-crossing time jump at multiple points within each major multi-step flow (listing→funding, funding→repayment, dispute lifecycle if A3 lands); each must either succeed correctly or fail with a clear, well-typed error — never with silent data loss or a panic. Out of scope: fixing every issue this harness might surface — file findings as follow-ups, prioritizing any silent-data-loss finding as critical/High severity immediately.
Implementation: Key files: contracts/tests/, builds on B40's TTL groundwork. Edge cases: this harness is itself only as good as the ledger-time-manipulation fidelity of the Soroban test environment — document any known simulation limitations. Testing: this issue's deliverable is the harness plus its initial findings report.
Complexity: High (200 points)
Program: Drips "Stellar Wave"
Description: Build a test harness that deliberately fast-forwards ledger sequence/time mid-multi-step-flow (e.g. between listing and funding, or between funding and repayment) to verify no in-flight operation is silently corrupted by an entry expiring at an inopportune moment — directly stress-testing B40's TTL-resilience guarantees under adversarial timing rather than just at rest.
Context: B40 checks that individual entries survive to their expected expiry; this harness specifically targets the more subtle case of an entry expiring in the middle of a multi-transaction user flow, which is a distinct and easily-missed failure mode.
Scope & Acceptance Criteria: Test scenarios injecting a TTL-boundary-crossing time jump at multiple points within each major multi-step flow (listing→funding, funding→repayment, dispute lifecycle if A3 lands); each must either succeed correctly or fail with a clear, well-typed error — never with silent data loss or a panic. Out of scope: fixing every issue this harness might surface — file findings as follow-ups, prioritizing any silent-data-loss finding as critical/High severity immediately.
Implementation: Key files:
contracts/tests/, builds on B40's TTL groundwork. Edge cases: this harness is itself only as good as the ledger-time-manipulation fidelity of the Soroban test environment — document any known simulation limitations. Testing: this issue's deliverable is the harness plus its initial findings report.Complexity: High (200 points)
Program: Drips "Stellar Wave"