View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010178 | Taler | wallet-core | public | 2025-07-12 11:36 | 2026-07-28 18:10 |
| Reporter | MarcS | 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 | high | Severity | feature | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Product Version | 1.0 stretch goals | ||||
| Target Version | 1.9 | ||||
| Summary | 0010178: Provide a fake/mocked history for screenshots [2d] | ||||
| Description | after scanning a QR code with some dev-experiment, wallet-core should switch into a "screenshot" mode where it reports a defined set of mocked transactions instead of the real database. The QR data will set the currency / exchange to be used (choosing a mock set from a few presets is sufficient, we don't need to encode the whole currency specifications in the QR talerURI). These transactions should not be static, but with dynamic timestamps, because our apps show relative times ("right now", "5 minutes ago", "yesterday", "last week"). When switching on this "screenshot mode", wallet-core should use the actual time to compute the mocked timestamps, to ensure that screenshots with relative dates look the same. We might probably even need some trigger to re-compute the timestamps - or just scan the QR code again? The user should be able to start actions (send, request, deposit, withdraw) because we need to screenshot them. It would be nice if the fake balance updates (i.e. gets decremented by the amount of a deposit or a p2p send), but that function can be added later. | ||||
| Tags | No tags attached. | ||||
| has duplicate | 0010412 | closed | implement dev experiment to fake transactions in the past | |
| child of | 0008351 | implementing | MarcS | Get screenshots from the latest actual mobile apps and the CHF exchange just before going live |
| child of | 0009935 | implementing | updated all outdated screenshots and keep them up-to-date |
| Ivan: is this something you can help with? | |
| Marc will specify for each screenshot the state of the wallet with what data to include. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-07-12 11:36 | MarcS | New Issue | |
| 2025-07-12 16:00 | Christian Grothoff | Note Added: 0025496 | |
| 2025-07-12 16:00 | Christian Grothoff | Status | new => implementing |
| 2025-07-12 16:00 | Christian Grothoff | Target Version | => 1.1 |
| 2025-07-12 16:00 | Christian Grothoff | Priority | normal => high |
| 2025-07-12 16:00 | Christian Grothoff | Severity | major => feature |
| 2025-07-12 16:01 | Christian Grothoff | Relationship added | child of 0008351 |
| 2025-07-29 22:48 | Christian Grothoff | Relationship added | child of 0009935 |
| 2025-07-30 09:16 | Christian Grothoff | Assigned To | => MarcS |
| 2025-07-30 09:16 | Christian Grothoff | Status | implementing => assigned |
| 2025-07-30 09:17 | Christian Grothoff | Note Added: 0025585 | |
| 2025-07-30 09:18 | Christian Grothoff | Summary | Provide a fake/mocked history for screenshots => Provide a fake/mocked history for screenshots [2d] |
| 2025-08-31 17:14 | Christian Grothoff | Target Version | 1.1 => post-1.0 |
| 2025-08-31 19:18 | Christian Grothoff | Assigned To | MarcS => |
| 2025-08-31 19:18 | Christian Grothoff | Status | assigned => implementing |
| 2025-08-31 19:18 | Christian Grothoff | Target Version | post-1.0 => 1.5 |
| 2025-12-07 09:36 | Christian Grothoff | Target Version | 1.5 => 1.8 |
| 2026-01-25 15:24 | Christian Grothoff | Target Version | 1.8 => 1.9 |
| 2026-07-28 18:10 | Florian Dold | Relationship added | has duplicate 0010412 |