rpc: Fix error wrapping chain in GetAccountLedgerSequence #136 #137
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.
What
Fixes the error handling in the GetAccountLedgerSequence function to correctly wrap ErrAccountNotFound, allowing proper error detection in the account sponsorship flow.
Why
Currently, when creating a sponsored account via /tx/create-sponsored-account, the process fails because the error wrapping is incorrect. The error check errors.Is(err, ErrAccountNotFound) fails since the error is returned as a plain string. This fix ensures the error is properly wrapped, allowing correct handling of missing accounts.
Known limitations
N/A
Issue that this PR addresses
Fixes: rpc: Fix error wrapping chain in GetAccountLedgerSequence #136
Priority: High
Checklist
PR Structure
Thoroughness
Release