Add Scopes into Transaction #2657
Closed
Conversation
This file contains 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
|
How do you decode it in a contract? |
Is not required to be decoded, you can hardcode the expected one, and don't allow anything else |
Ashuaidehao
reviewed
Mar 8, 2022
|
I think we should create a new syscall, and decode |
|
Merged
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.
It's required to have access to the transaction's scopes inside the smart contract in certain cases, I thought about create a new syscall, check if a witness it will be valid, but it depend of the callingscript, executionscript, in fact the whole ExecutionEngine...
I want to check inside my verify if the transaction was signed by the user.