View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010892 | Taler | exchange | public | 2026-01-19 17:06 | 2026-02-04 19:00 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 1.4 | Fixed in Version | 1.4 | ||
| Summary | 0010892: exchange should ensure that the set of newly signed denom keys is anchored at the same (withdrawal) start time | ||||
| Description | This allows the wallets (and linter tooling) to easily assess that exchange has indeed properly done the (offline) denom key signing. If newly signed denoms are not anchored at the same start time, wallets can't distinguish between the following scenarios: (a) The exchange dropped/changed the denom config (e.g. offers fewer denominations) (b) The exchange operator forgot to offline-sign and upload new denominations | ||||
| Tags | No tags attached. | ||||
| related to | 0010893 | informing | Florian Dold | wallet should check that exchange signed sufficient denom keys before withdrawal/refresh |
| I guess to really ensure this, we need technically need to take all the withdrawal durations, compute the lcm, and sign at least that far ahead into the future. Right? | |
| Yes, it'll be a bit complicated, but totally doable. | |
| Fixed in b7e6a5b57..32c617992 | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-01-19 17:06 | Florian Dold | New Issue | |
| 2026-01-19 17:07 | Florian Dold | Summary | exchange should ensure that the set of newly signed denom keys is anchored at the same start time => exchange should ensure that the set of newly signed denom keys is anchored at the same (withdrawal) start time |
| 2026-01-19 17:09 | Florian Dold | Relationship added | related to 0010893 |
| 2026-01-19 17:16 | Florian Dold | Note Added: 0027283 | |
| 2026-01-20 11:44 | Christian Grothoff | Status | new => implementing |
| 2026-01-20 11:44 | Christian Grothoff | Target Version | => 1.8 |
| 2026-01-20 11:44 | Christian Grothoff | Note Added: 0027290 | |
| 2026-01-25 15:22 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2026-01-25 15:22 | Christian Grothoff | Status | implementing => assigned |
| 2026-01-25 15:23 | Christian Grothoff | Status | assigned => implementing |
| 2026-02-01 17:14 | Christian Grothoff | Status | implementing => assigned |
| 2026-02-02 08:50 | Christian Grothoff | Status | assigned => informing |
| 2026-02-02 08:50 | Christian Grothoff | Resolution | open => fixed |
| 2026-02-02 08:50 | Christian Grothoff | Fixed in Version | => 1.4 |
| 2026-02-02 08:50 | Christian Grothoff | Note Added: 0027537 | |
| 2026-02-02 08:50 | Christian Grothoff | Product Version | => git (master) |
| 2026-02-02 08:50 | Christian Grothoff | Target Version | 1.8 => 1.4 |
| 2026-02-04 19:00 | Christian Grothoff | Status | informing => closed |