Fix smart contract addressing and storage #177
Conversation
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
This commit fixes the following issues: - New contract addresses are generated with a random nonce instead of 0. This allows an account owner to deploy multiple contracts without address conflict. - When storing, GlobalView passes both the contract address and the key argument to the underlying storage as key instead of just the key argument. This allows different instances of the same contract to store separate state values under the same state name. - Update eEVM dependency. - In contract_tools, I added the missing ":f:" to getopt_long. This allows users to pass config file to contract_tools. - Remove the merge conflict markers from start_contract_service.sh
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 commit fixes the following issues:
start_contract_service.sh.