Separate receiver and sender logic in steps #13
Merged
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, except for some other very small improvements, mainly separates the logic that has to be done on the receiver's side from the logic needed to be done on the sender's side. Before, the response of the receiver was done in the same step as processing that response with the sender's wallet, now there is one step where the receiver creates and signs its response psbt and then the last step is the sender processing the response, signing it and broadcasting it. With this separation it is easier to understand for someone looking at the example to implement it correctly in its own app.