-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.0 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error #683
Comments
Duplicate of #455 |
We use bounties to incentivize development and reward contributors. All issues available for a bounty have the To receive the bounty of this issue, you agree to these conditions:
|
@delta1 Would you be interested in taking this on? |
Yes definitely! Will pick it up after getting #1081 fixed and released for the hard fork |
I did start working on this a bit. I'll publish my WIP branch later, if @delta1 or anyone else wants to pick up from where I left |
Yeah was taking a look! Happy to pick it up - please share your branch name |
Increased bounty to 0.5 XMR! @delta1 @lescuer97 |
Nice! Picking this back up tomorrow 👌 |
Any updates? Have you had time to take a look at this again? |
No updates, sorry have been dealing with personal issues so if somebody else could pick it up that’s totally fine. Otherwise I can get back to it in a couple of weeks. |
I'm increasing the bounty to 1 XMR because I believe this will provide some major benefits in terms of usability! @lescuer97 @delta1 @ALL |
I'm interested, can I try to implement this? |
sure @thenhnn go ahead |
Can you check #1688, please? |
As discovered in #674, users may try to refund a swap even though that is no longer possible because Alice already punished.
We should catch this case by parsing the error message returned from electrum and display something more informative to the user.
Also, we need to advance the internal state to correctly reflect what happened on the blockchain, otherwise
swap list
returns misleading information.The text was updated successfully, but these errors were encountered: