View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010134 | Taler | wallet (all platforms) | public | 2025-06-25 09:58 | 2025-06-29 08:24 |
| Reporter | oec | 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 | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0010134: Abstract away choice of location of DB for UI-devs | ||||
| Description | IIUC, right now, the UI-developer of the wallet also chooses the location of the DB for the coins and is responsible for its protection. To reduce the burden on the UI developers and to ensure that the best and most secure, platform specific location and protection is chosen for the DB, this code should be provided by each of the platform specific layers on top of wallet-core. This is not a trivial task as the choices will depend on the platform _and_ particular versions of those. Therefore, somebody (both, person and code location) needs to take the time and care and be responsible for making the best choice. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-25 09:58 | oec | New Issue | |
| 2025-06-29 08:24 | Christian Grothoff | Status | new => implementing |
| 2025-06-29 08:24 | Christian Grothoff | Target Version | => post-1.0 |