-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/support non fungibles in execution trace #2042
base: develop
Are you sure you want to change the base?
Feature/support non fungibles in execution trace #2042
Conversation
With `recall` it is not possible to determine the account the resources are recalled from, because recall operates with internal vault.
c2b367a
to
041d7ee
Compare
Docker tags |
Benchmark for b7d7f93Click to view benchmark
|
2a38ea3
to
a4629ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thanks :)
TakeAdvanced(ResourceAddress, Decimal), | ||
Recall(ResourceAddress, Decimal), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth mentioning that Recall is not supported (and why)?
And perhaps (somewhere) that this feature isn't comprehensive/a good abstraction, and will be deprecated in the node's Core API at Dugong, with the intention to have it removed at a later point?
Summary
ExecutionTrace
resource changesExecutionTrace
resource changesWith
recall
it is not possible to determine the account the resources are recalled from, becauserecall
operates with internal vault.Testing
Relevant tests added