View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004005 | Taler | wallet (WebExtension) | public | 2015-10-13 20:55 | 2016-02-19 20:33 |
| Reporter | Marcello Stanisci | 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 | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004005: Mark reserve as "defunct" after successful withdrawal | ||||
| Description | Inhibit the reserve, by marking it as empty or by removing it (from DB), after the wallet withdraws all the money in it. | ||||
| Tags | No tags attached. | ||||
| In the current implementation, the reserve has the three columns 'value, fraction, currency' indicating the amount wired to the mint for its creation. Since every withdrawal goes asynchronously, there is no "central" point where it would be possible to detect whether any withdrawal went fine. A solution might be that each withdrawal just subtracts its amount from the reserve's. That way, if the amount drops to zero, then the reserve's row could be deleted (or accordingly managed), otherwise, the wallet maintains a reference to a non-emptied reserve (still to be accordingly managed). | |
| Actually, that doesn't work as you don't know if the user deposited more than indicated, or did another deposit later. The safest thing to do is to have a timeout, i.e. reserve not used for x months, and then check /reserve/status and if it is zero and the reserve has been unused for like a year, then we can drop the column. | |
| This should already work in the WebEx wallet. It needs more testing though ... | |
| Reserves in the WebEx wallet are not directly visible in the UI, all coins are automatically withdrawn. Once 0004126 and 0004188 are fixed, reserves will always be completely emptied (even with restarts inbetween) and then deleted. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-10-13 20:55 | Marcello Stanisci | New Issue | |
| 2015-10-13 20:55 | Marcello Stanisci | Status | new => assigned |
| 2015-10-13 20:55 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2015-10-14 11:10 | Marcello Stanisci | Note Added: 0009727 | |
| 2015-10-16 14:21 | Marcello Stanisci | Target Version | => 0.1 |
| 2015-10-17 22:58 | Christian Grothoff | Note Added: 0009740 | |
| 2015-10-22 23:13 | Christian Grothoff | Product Version | => 0.0 |
| 2016-01-22 12:33 | Marcello Stanisci | Assigned To | Marcello Stanisci => Florian Dold |
| 2016-01-22 12:33 | Marcello Stanisci | Category | wallet (browser-based) => wallet (WebExtensions) |
| 2016-02-01 14:57 | Florian Dold | Note Added: 0010124 | |
| 2016-02-18 23:54 | Florian Dold | Note Added: 0010158 | |
| 2016-02-18 23:54 | Florian Dold | Status | assigned => informing |
| 2016-02-18 23:54 | Florian Dold | Resolution | open => no change required |
| 2016-02-19 20:33 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2016-02-19 20:33 | Christian Grothoff | Target Version | 0.1 => 0.0 |
| 2016-02-19 20:33 | Christian Grothoff | Status | informing => closed |
| 2023-04-13 18:37 | Florian Dold | Category | wallet (WebExtensions) => wallet (WebExtension) |