Adapt to Script Hash Identification Change #82
Merged
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
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.
This PR adapts neo debugger to changes introduced by neo-project/neo#2044
In particular, this change adds a new
IExecutionContext.ScriptIdentifierproperty. This property represents the script hash identifier generated when a contract is deployed to the blockchain.IExecutionContext.ScriptHashis the SHA 256 hash of the contract binary. Both are needed in neo debugger - the former is how contracts are identified by the contract execution engine and contract state table. The latter is used for mapping contracts to debugger information.