View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007319 | Taler | specification | public | 2022-09-02 20:04 | 2024-01-12 13:03 |
| Reporter | sebasjm | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0007319: The sender should be able to cancel an invoice or transfer before the recipient pays or withdraws | ||||
| Description | As a sender of a transfer, I want to be able to cancel and get the money back (without fee) before the recipient withdraws As a sender of an invoice, I want to be able to cancel and avoid the contract to be paid before the recipient pays. From email discussion: "we could add a DELETE endpoint to the exchange for this. But, a bit tricky: we'd need the wallet to do a long-polling GET while showing the pending transaction anywhere in the UI to notice removal and then hide it. Also, if we truly DELETE on the exchange side (which seems best), we'd have no data to share with the recipient (or auditor) about the deletion, so we'd only have the refresh fees (and a malicious actor may not refresh) and maybe the purse fees" | ||||
| Tags | No tags attached. | ||||
| duplicate of | 0007584 | closed | Florian Dold | implement aborting p2p pull payments |
| has duplicate | 0007461 | closed | Christian Grothoff | allow user to cancel push/pull payments |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-09-02 20:04 | sebasjm | New Issue | |
| 2022-09-02 20:04 | sebasjm | Status | new => assigned |
| 2022-09-02 20:04 | sebasjm | Assigned To | => Christian Grothoff |
| 2022-09-17 20:50 | Christian Grothoff | Priority | normal => low |
| 2022-09-17 20:50 | Christian Grothoff | Status | assigned => acknowledged |
| 2022-09-17 20:50 | Christian Grothoff | Target Version | git (master) => |
| 2022-09-17 20:50 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2022-11-16 16:36 | Christian Grothoff | Relationship added | has duplicate 0007461 |
| 2022-11-16 16:37 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-11-16 16:37 | Christian Grothoff | Status | acknowledged => assigned |
| 2022-12-29 23:36 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2022-12-29 23:36 | Christian Grothoff | Note Added: 0019545 | |
| 2023-02-17 01:41 | Florian Dold | Target Version | => 0.9.2 |
| 2023-02-17 17:08 | Florian Dold | Target Version | 0.9.2 => 0.9.3 |
| 2023-04-05 16:25 | Florian Dold | Status | assigned => informing |
| 2023-04-05 16:25 | Florian Dold | Resolution | open => duplicate |
| 2023-04-05 16:25 | Florian Dold | Note Added: 0020030 | |
| 2023-04-05 16:25 | Florian Dold | Relationship added | duplicate of 0007584 |
| 2023-04-05 16:25 | Florian Dold | Note Edited: 0020030 | |
| 2023-09-23 13:07 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-09-23 13:09 | Christian Grothoff | Status | informing => closed |
| 2024-01-12 13:03 | Christian Grothoff | Category | exchange API (HTTP specification) => specification |