View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007978 | Taler | wallet-core | public | 2023-11-13 15:38 | 2025-04-17 22:11 |
| Reporter | Florian Dold | 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 | normal | Severity | feature | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0007978: store transaction events when changing transaction details | ||||
| Description | Whenever we destructively adjust something in a transaction, we should store this change in a transaction events object store. Such changes can, for example, happen when a withdrawal is re-denominated, or when a payment needs to be repeated with a different coin selection due to accidental double spending. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-13 15:38 | Florian Dold | New Issue | |
| 2023-11-13 15:38 | Florian Dold | Status | new => assigned |
| 2023-11-13 15:38 | Florian Dold | Assigned To | => Florian Dold |
| 2023-11-13 19:40 | Florian Dold | Target Version | 0.10 => post-1.0 |
| 2025-04-17 22:11 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-04-17 22:11 | Christian Grothoff | Status | assigned => implementing |