Skip to content
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

Closed
thomaseizinger opened this issue Aug 24, 2021 · 16 comments · Fixed by #1668
Assignees
Labels
Bounty 💰 The first person to fix this issue will be awarded a reward enhancement New feature or request Priority 1 This issue is top-priority at the moment

Comments

@thomaseizinger
Copy link
Contributor

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.

@thomaseizinger thomaseizinger added the enhancement New feature or request label Aug 24, 2021
@da-kami
Copy link
Member

da-kami commented Aug 25, 2021

Duplicate of #455

@da-kami da-kami marked this as a duplicate of #455 Aug 25, 2021
@rishflab rishflab self-assigned this Oct 8, 2021
@binarybaron binarybaron changed the title Provide better error message when punish has been triggered Provide better feedback when cancel/refund transaction publish fails by parsing electrum error Jul 26, 2022
@binarybaron binarybaron changed the title Provide better feedback when cancel/refund transaction publish fails by parsing electrum error [0.2 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error Aug 4, 2022
@binarybaron binarybaron added the Bounty 💰 The first person to fix this issue will be awarded a reward label Aug 4, 2022
@binarybaron
Copy link
Collaborator

We use bounties to incentivize development and reward contributors. All issues available for a bounty have the Bounty 💰 label.

To receive the bounty of this issue, you agree to these conditions:

  • Your changes must follow the styling guidelines.
  • Bounties will be set and awarded at discretion of @binarybaron .
    The issues eligible for a bounty are labelled 'Bounty 💰' and have the amount of the bounty specified in the title in this form: [1 XMR].
  • An issue is considered resolved when the patch(es) proposed by the contributor is/are merged in the appropriate repository according to terms of the issue.
  • The first person who resolves an issue in its entirety will receive the entire amount of the bounty.
  • If the issue is resolved collaboratively by more than one person, the reward will be distributed among the contributors
  • Let the Maintainers know if you intend to work on a bounty, so that the issue can be assigned to you. Being assigned to an issue doesn't make that issue resolvable only by the assignee. It's meant to avoid duplication of efforts and not to discourage collective works.
  • After the issue is resolved, contact @binarybaron and claim your bounty (remember to provide them with a Monero address).

@binarybaron
Copy link
Collaborator

@delta1 Would you be interested in taking this on?

@delta1
Copy link
Collaborator

delta1 commented Aug 4, 2022

Yes definitely! Will pick it up after getting #1081 fixed and released for the hard fork

@delta1 delta1 assigned delta1 and unassigned rishflab Aug 9, 2022
@binarybaron
Copy link
Collaborator

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

@delta1
Copy link
Collaborator

delta1 commented Aug 10, 2022

Yeah was taking a look! Happy to pick it up - please share your branch name

@binarybaron
Copy link
Collaborator

@binarybaron binarybaron changed the title [0.2 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error [0.5 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error Sep 12, 2022
@binarybaron
Copy link
Collaborator

Increased bounty to 0.5 XMR! @delta1 @lescuer97

@delta1
Copy link
Collaborator

delta1 commented Sep 12, 2022

Nice! Picking this back up tomorrow 👌

@binarybaron
Copy link
Collaborator

Any updates? Have you had time to take a look at this again?

@delta1
Copy link
Collaborator

delta1 commented Sep 28, 2022

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.

@binarybaron binarybaron changed the title [0.5 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error [1.0 XMR] Provide better feedback when cancel/refund transaction publish fails by parsing electrum error Jun 6, 2023
@binarybaron
Copy link
Collaborator

binarybaron commented Jun 6, 2023

I'm increasing the bounty to 1 XMR because I believe this will provide some major benefits in terms of usability! @lescuer97 @delta1 @ALL

@thenhnn
Copy link

thenhnn commented Mar 6, 2024

@binarybaron I'm increasing the bounty to 1 XMR because I believe this will provide some major benefits in terms of usability!

I'm interested, can I try to implement this?

@delta1
Copy link
Collaborator

delta1 commented Mar 6, 2024

sure @thenhnn go ahead

@thenhnn
Copy link

thenhnn commented Mar 6, 2024

@delta1 sure @thenhnn go ahead

Please check #1571

@patrini32
Copy link
Contributor

patrini32 commented Jun 4, 2024

Can you check #1688, please?

binarybaron pushed a commit that referenced this issue Jul 1, 2024
…user (#1668)

We now display the reason for a failed cancel-refund operation to the user.

Fixes #683
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bounty 💰 The first person to fix this issue will be awarded a reward enhancement New feature or request Priority 1 This issue is top-priority at the moment
Projects
None yet
7 participants