View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010314 | Taler | wallet (all platforms) | public | 2025-08-29 19:28 | 2025-08-30 23:11 |
| Reporter | mikolai | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Summary | 0010314: Better UX when deployment has been reset (changed master key) | ||||
| Description | The current UX when coming to the Datenspuren 2025 after being here last year and not deleting the Taler wallet app in-between is the following: 1. get non-accurate error messages as reported in https://bugs.gnunet.org/view.php?id=10305 2. need to delete the exchange manually from the list (settings > payment providers) 3. need to add the exchange manually again (or by scanning a withdraw-exchange URI) From a user point of view, I would prefer: 1. a fullscreen error screen reporting that the deployment seems to have changed in between 2. provide an option to directly do step 2 and 3 in one (point out that the balance will be zeroed, but that there is no other way of using this exchange again) That's something we could include in the Taler wallet tutorial. The current steps are quite tedious and hard to convey. | ||||
| Tags | No tags attached. | ||||
|
|
Well, you are REALLY not supposed to loose your master public key. I mean, it's the master key for a payment system... |
|
|
Sure, but it was always meant to be a temporary deployment. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-08-29 19:28 | mikolai | New Issue | |
| 2025-08-29 20:50 | Christian Grothoff | Note Added: 0025745 | |
| 2025-08-29 20:50 | Christian Grothoff | Severity | major => feature |
| 2025-08-29 20:50 | Christian Grothoff | Status | new => acknowledged |
| 2025-08-30 23:11 | mikolai | Note Added: 0025748 |
