Feature/135 transaction impact simulator#175
Merged
Just-Bamford merged 2 commits intoJun 30, 2026
Merged
Conversation
|
@Oluwasuyi-Timilehin 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.
#closes #135
Description
This PR resolves issue #135 by adding a dry-run transaction impact simulator (
simulateTransactionImpact) to thesorokit-coretransaction module. This allows developers and wallets to predict liquid asset balance changes (both native XLM and credit trustline assets) for a given account before committing and submitting the transaction to the network.In alignment with the ecosystem's design principles, this feature is completely stateless, framework-agnostic, and implements the no-throw result model, cleanly packaging errors into
SorokitResultvalues rather than throwing exceptions.Changes
src/transaction/index.tssimulateTransactionImpact(publicKey, transactionXdr).TransactionBuilder.fromXDR.paymentandcreateAccountmutations.mutateAssetBalance) to calculate precision updates cleanly.src/tests/transaction.test.tssimulateTransactionImpact.SorokitResult<"error">layout standards.Verification Results
Automated Unit Tests
Executed
vitestsuite to verify execution stability: