Separate tokenReceived
for Stellar Asset Contract
#139
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.
This is a delta to #135.
While working on #133, I realized that Stellar Asset Contracts use a different storage layout than the
soroban-examples/token
contract (in particular, they keep a struct inside theBalance
storage, not just ani128
amount).In this PR, we
tokenTransferred
condition that only applies tosoroban-examples/token
out of Solarkraft, and intoverify_js_example.ts
tokenTransferred
insteadtokenReceived
, that checks only the receiver part oftokenTransferred
tokenReceived
is necessary, because there may not be a sender balance recorded in contract storage of the SAC if the sender is transferring native tokens.