fix: make bet placement atomic across fee and state writes - #1431
Merged
greatest0fallt1me merged 1 commit intoAug 30, 2026
Merged
Conversation
|
@Hakimziyech18 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! 🚀 |
greatest0fallt1me
merged commit Aug 30, 2026
30062eb
into
Predictify-org:master
2 of 3 checks passed
6 tasks
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
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.
Summary
Makes single bet placement atomic across fee validation, fund locking, and bet-related state writes.
The placement flow now completes all predictable validation and fallible arithmetic before transferring user funds. Once funds are locked, the contract only commits state values that were already prepared successfully.
Changes
place_betpublic interface and existing duplicate-bet protection.Atomicity / failure handling
The single-bet flow is now ordered as:
Arithmetic overflow and other predictable validation failures therefore occur before funds are moved.
Soroban transaction semantics continue to provide transaction-level rollback for host-level failures during the commit phase.
Retries after a successful placement remain deterministic because the existing one-bet-per-user-per-market invariant returns
AlreadyBetinstead of applying the bet again.Compatibility
No public contract interface or persisted data type was changed.
Existing callers of
place_betremain compatible.No dependency changes are required.
Tests
Added focused regression coverage for:
Closes #1395
Validation commands: