View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007917 | Taler | exchange | public | 2023-08-11 14:40 | 2024-08-12 08:00 |
| Reporter | Christian Grothoff | Assigned To | 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 | none | Severity | feature | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-2.0 | ||||
| Summary | 0007917: change applicablility of refresh fees | ||||
| Description | We may want to consider only charging a refresh fee if the target denomination is for the same amount, effectively waiving the refresh fee when getting change or refunds. This would make the STEFAN proposal (DD47) more effective and fees more predictable. This will require non-trivial changes to the exchange and auditor. There is zero impact on production systems as long as they use a refresh fee of 0 (as suggested for now). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-08-11 14:40 | Christian Grothoff | New Issue | |
| 2023-08-11 14:40 | Christian Grothoff | Status | new => assigned |
| 2023-08-11 14:40 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2023-08-11 14:41 | Christian Grothoff | Status | assigned => implementing |
| 2023-08-11 14:41 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2024-08-12 08:00 | Christian Grothoff | Target Version | post-1.0 => post-2.0 |