Fix asset code case sensitivity - Stellar asset codes are case-sensitive but we were converting all codes to uppercase causing issues with trust lines #943
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
Fixed asset code case sensitivity in the CreateAsset handler. Previously, all asset codes were converted to uppercase using 'strings.ToUpper()', but Stellar asset codes are case-sensitive. This caused issues when users entered assets with lowercase letters leading to trustline mismatches. The fix preserves the exact case entered by users while still using case-insensitive comparison for native XLM asset validation.
Why
Stellar asset codes are case-sensitive identifiers. When users create assets with mixed case (like 'USDM0a'), the system was converting them to uppercase ('USDM0A'), which could cause issues when the actual asset on-chain has a different case or users try to add trustlines that don't match the stored case.
Known limitations
N/A
Checklist
SDP-1234: Add new featureorChore: Refactor package xyzformat. The Jira ticket code was included if available.CHANGELOG.mdis updated (if applicable)