View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008538 | Taler | wallet-core | public | 2024-02-28 01:07 | 2025-04-17 22:29 |
| 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 | tweak | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0008538: consider removing exchange details pointer in the wallet-core DB | ||||
| Description | We used to have this weird concept (that came up during CRDT-style backups) that an exchange can have *multiple* details (master pub, keys, ...) associated with it, where just one of the details is the current one. It's unnecessarily complex, we might want to scrap it and simplify the code/DB. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-28 01:07 | Florian Dold | New Issue | |
| 2024-02-28 01:07 | Florian Dold | Status | new => assigned |
| 2024-02-28 01:07 | Florian Dold | Assigned To | => Florian Dold |
| 2024-07-25 22:02 | Christian Grothoff | Target Version | 1.0 => post-1.0 |
| 2024-07-28 19:52 | Christian Grothoff | Severity | minor => tweak |
| 2025-04-17 22:29 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-04-17 22:29 | Christian Grothoff | Status | assigned => implementing |