View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007269 | Taler | exchange API (HTTP specification) | public | 2022-07-05 11:23 | 2022-11-04 20:52 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | low | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.9 | Fixed in Version | 0.9 | ||
| Summary | 0007269: forcing reserve closure is not implemented | ||||
| Description | The question is if we want this, and if so some details (like should we include a timestamp from the client, and if so what does that timestamp signify) should be discussed. Forcing reserve closure might be a nice feature if we have otherwise long-lived reserves for which auto-closure is not implemented. Goes together with discussions about accounts, account fees and the number of purses an account can create 'for free'. | ||||
| Tags | No tags attached. | ||||
|
|
What is now missing is the auditor support -- and more testing. |
|
|
Now supported by auditor. More testing will require wallet/merchant support first. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-05 11:23 | Christian Grothoff | New Issue | |
| 2022-07-05 11:23 | Christian Grothoff | Status | new => assigned |
| 2022-07-05 11:23 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-07-05 13:20 | Christian Grothoff | Priority | normal => low |
| 2022-10-20 12:25 | Christian Grothoff | Note Added: 0019259 | |
| 2022-11-03 00:11 | Christian Grothoff | Status | assigned => resolved |
| 2022-11-03 00:11 | Christian Grothoff | Resolution | open => fixed |
| 2022-11-03 00:11 | Christian Grothoff | Fixed in Version | => 0.9 |
| 2022-11-03 00:11 | Christian Grothoff | Note Added: 0019350 | |
| 2022-11-03 00:11 | Christian Grothoff | Target Version | => 0.9 |
| 2022-11-04 20:52 | Christian Grothoff | Status | resolved => closed |
