Change extrinsic submission flow #1760
Open
+507
−389
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 changes the flow of extrinsic submission.
Currently, the flow suffers from a double-compose issue.
Current flow if the submission has an exception
(assume the initial submission is included in the chain, regardless of the client exception):
_do_transferIn the above example, now there have been 2 valid transfer extrinsics submitted (and included) to the chain
This is bad, this is a double-send by the Python API
This PR changes the flow to retry only the submission portion. (i.e., 6. retries from 4.)