View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007847 | Taler | wallet-core | public | 2023-05-23 15:24 | 2026-09-19 14:42 |
| Reporter | sebasjm | Assigned To | Florian Dold | 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 | unable to reproduce |
| Status | closed | Resolution | duplicate | ||
| Product Version | git (master) | ||||
| Target Version | 1.6 | Fixed in Version | 1.6 | ||
| Summary | 0007847: DoS when all wallet try to refresh coins at the same time | ||||
| Description | Instead of wallet doing refresh exactly 3 months before expiration time, it should refresh based on a random value close to 3 months From email > The refresh transaction is automatically triggered by the wallet software 3 months before the end of the validity of a coin. Especially if Exchange > operators charge refresh fees, the fact that a fee may automatically be charged in the background without user interaction is likely particularly > difficult to explain. > But that also means that "3 months before the end of the validity of a coin" will be the same for every wallet since the beginning, > isn't this a self-DOS waiting for us? > I mean, all the wallet with all those coins will try to refresh at the same time. > Maybe refresh time should random time based in a normal distribution with mean expiration_time - 2 month and std_dev 1 month | ||||
| Tags | performance | ||||
| duplicate of | 0006563 | informing | Florian Dold | document recommended rules for wallet's auto-refresh |
| Duplicate of issue 0006563, which asks for a spec for auto-refresh. There's already a draft that considers the issue raised by Sebastian. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-23 15:24 | sebasjm | New Issue | |
| 2023-05-23 15:24 | sebasjm | Status | new => assigned |
| 2023-05-23 15:24 | sebasjm | Assigned To | => Florian Dold |
| 2023-09-03 12:54 | Christian Grothoff | Severity | major => feature |
| 2023-12-22 14:02 | Christian Grothoff | Target Version | 1.0 => post-1.0 |
| 2025-04-17 22:09 | Christian Grothoff | Tag Attached: performance | |
| 2025-04-17 22:09 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-04-17 22:09 | Christian Grothoff | Status | assigned => implementing |
| 2026-08-22 18:59 | Florian Dold | Assigned To | => Florian Dold |
| 2026-08-22 18:59 | Florian Dold | Status | implementing => closed |
| 2026-08-22 18:59 | Florian Dold | Resolution | open => duplicate |
| 2026-08-22 18:59 | Florian Dold | Note Added: 0029569 | |
| 2026-08-22 18:59 | Florian Dold | Relationship added | duplicate of 0006563 |
| 2026-09-19 14:42 | Christian Grothoff | Fixed in Version | => 1.6 |
| 2026-09-19 14:42 | Christian Grothoff | Target Version | post-1.0 => 1.6 |