This repository has been archived by the owner on Jun 21, 2020. It is now read-only.
BUG: fix nonce for concurrency tasks #193
Open
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Continues the work initiated in #181, this PR implements the true intent of that first PR, tracking locally nonces used that are submitted concurrently too quickly before the contract can update them. The exception is the
Contract Deploymentwhere the nonce has to be the "true" nonce in sync with the contract, otherwise the contract will throw an error. In all other cases (compute task), the nonces do not need to be in sync.Please note that the contract and EnigmaJS DO NOT support concurrency in contract deployments, only in computations.