fix: handle cross-contract asset transfer failures with explicit checks (#104)#148
Open
Nanle-code wants to merge 3 commits into
Open
fix: handle cross-contract asset transfer failures with explicit checks (#104)#148Nanle-code wants to merge 3 commits into
Nanle-code wants to merge 3 commits into
Conversation
…ks (StellarYield#104) - Add Error::InsufficientVaultBalance variant for clearer diagnostics - Add explicit balance checks before all outgoing transfers in transfer_asset_from_vault - Wrap transfer_asset_to_vault to catch insufficient user balance scenarios - Add vault_asset_balance() public view function for frontend solvency verification - Document atomicity assumptions in all functions combining state changes with external calls - Add comprehensive tests for insufficient balance scenarios Addresses vault state inconsistency when token transfers fail by providing explicit balance checks and clear error diagnostics instead of opaque token contract failures.
|
@Nanle-code 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
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.
Problem Summary
Issue #104 identified that cross-contract asset transfer failures were not properly handled, potentially leaving vault states inconsistent. Token transfer failures resulted in opaque error messages, and the code relied on implicit atomicity guarantees without documentation.
Solution Overview
This PR implements comprehensive error handling for asset transfer failures with explicit balance checks, clear error diagnostics, and documented atomicity assumptions.
Key Changes
1. Enhanced Error Handling
Error::InsufficientVaultBalancefor vault-specific failures2. Atomicity Documentation
Added explicit atomicity documentation to all functions combining state changes with external calls:
3. Frontend Integration
4. Comprehensive Testing
Added 8 new test functions covering all insufficient balance scenarios:
Security Benefits
Definition of Done
Testing
All new tests pass and verify proper error handling without state corruption. The implementation maintains backward compatibility while providing enhanced safety and clarity.
Files Modified
This implementation fully addresses the core issue of cross-contract asset transfer failures and ensures vault state consistency under all failure scenarios.
Closes #104