Conversation
|
@Peolite1 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.
Title
Fix initial balance and authorized caller storage serialization (Closes #1104)
Description
This PR fixes a bug in the Vault contract initialization where
initial_balanceandauthorized_caller(which are passed asOptiontypes) were being written to instance storage natively asOptiontypes. This caused a downstream deserialization failure during subsequent getter calls since the contract functions (e.g.,deposit,deduct,balance) expect those fields to be resolved primitive types (likei128andAddress).Changes Made
initial_balance: We now gracefully unwrapinitial_balanceduringinitusing.unwrap_or(0)before writing it toDataKey::Balanceas a plaini128.VaultError::InitialBalanceNegativeif the resolved initial balance evaluates to a negative integer.AuthorizedCallerStorage: Fixed a similar discrepancy withDataKey::AuthorizedCaller. We now conditionally save the underlyingAddressifSomeis provided, preventingScVal::Void/Optionmismatch failures down the line.init_none_initial_balance_allows_deposit_and_deduct) tocontracts/vault/src/test_init_hardening.rsthat explicitly initializes the vault with aNonebalance and verifies that both subsequentdeposit()anddeduct()calls correctly run and report valid math.Security and Failure-Mode Handling
Writing
ScVal::Voidinto instance storage could permanently brick newly deployed vaults since the first deposit or deduction would fail parsing the storage slot intoi128. By strictly converting these arguments into their plain primitive types at initialization, we eliminate the runtime crash and restore resilient type safety across the vault's core logic.Closes #1104