Summary
V1's scripts/testnet-load.sh exercises simple, single-party dispute volume. V2 needs its own load test that actually exercises many concurrent third-party positions on a single dispute, and multiple disputes running concurrently, since that's the scenario v2 adds that v1 never had.
What to build
A script (following the pattern of scripts/testnet-smoke.sh and scripts/testnet-load.sh) that, against a real testnet deployment:
Depends on
#65-#70 (needs the full assert-through-withdraw lifecycle working).
Summary
V1's scripts/testnet-load.sh exercises simple, single-party dispute volume. V2 needs its own load test that actually exercises many concurrent third-party positions on a single dispute, and multiple disputes running concurrently, since that's the scenario v2 adds that v1 never had.
What to build
A script (following the pattern of scripts/testnet-smoke.sh and scripts/testnet-load.sh) that, against a real testnet deployment:
W-tracking and per-position storage from [Feature] V2: implement dispute and third-party registration #66) from distinct funded testnet identities.Depends on
#65-#70 (needs the full assert-through-withdraw lifecycle working).