Add precision-safe i128/u128 to bigint conversion layer - #144
Merged
meshackyaro merged 2 commits intoAug 30, 2026
Merged
Conversation
|
@defimomof2 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
2 participants
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.
src/utils/i128.ts— bigint-firsttoI128ScVal/toU128ScVal/fromI128ScVal/fromU128ScVal, with explicit sign/overflow range checks and rejection of non-integer or precision-losing inputs (no silent rounding). Round-tripped through actual XDR bytes (not just in-memory ScVal) intests/i128.test.ts, including both types' min/max boundaries. Closes Precision-Safe i128/u128 ⇄ Native Conversion Layer #67