Test/escrow fuzz funding sequences#135
Merged
mikewheeleer merged 6 commits intoLiquifact:mainfrom Apr 1, 2026
Merged
Conversation
|
@nanaabdul1172 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #32 #135
The escrow test suite now includes high-variance randomized funding-sequence validation to strengthen confidence in invariant stability under realistic and adversarial contribution patterns, including varied actor counts, mixed contribution sizes, and long shuffled funding sequences. These tests verify that funded_amount is monotonic, that escrow status transitions occur only at the correct funding threshold, and that the sum of per-investor contributions always matches aggregate funded state, preventing accounting drift across complex execution paths. To support reproducibility and incident triage, failing randomized runs can be replayed deterministically using fixed PROPTEST_CASES and PROPTEST_SEED values, enabling exact local reproduction of CI failures while preserving broad scenario coverage for security-focused regression testing.