View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004840 | Taler | exchange | public | 2016-12-16 09:02 | 2017-10-18 13:42 |
| Reporter | Marcello Stanisci | 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 | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.4 | Fixed in Version | 0.4 | ||
| Summary | 0004840: /keys cherry picking | ||||
| Description | Problem about the signature of the cumulative hash of al DKs, namely the 'eddsa_sig' field sent along in the /keys response: (1) it makes it difficult to optimize the /keys response. I.e. we might want to leave out DKs that the wallet already knows. If the wallet were to tell us: only send DKs later than XXX (timestamp), we could possibly save a LOT of bandwidth. If we want to do this optimization, we need a different way to indicate which set of keys the signature is over (if the client already has the DKs, they can obviously be included in the hash, but we still need an _efficient_ way to communicate the set of DKs to use, i.e. by numbering them per-exchange). Future work... | ||||
| Tags | No tags attached. | ||||
| Relating to 0003887 as having 0003887 also changes /keys and cherry-picking. | |
| First bits of spec and logic pushed, actual implementation(s) in exchange and exchange-lib still missing, but marked with 0004840. | |
| 7d21331..7aa23a3 adds cherry picking support to the exchange-lib/ code. | |
| 7aa23a3..6d7645a _might_ complete the implementation, but it VERY BADLY needs an automated test. The test should have the API download /keys, generate more keys, SIGNAL the exchange HTTPD to reload the keys, then do the incremental download, and finally show that the new denomination keys (and auditor signatures) were merged in properly. | |
| Test implemented (plus bugfixes) in f440904..f346e89 | |
| Code is implemented and could be used by the wallet. However, leaving the bug open as it is in need for a clean-up. | |
| Code completed and cleaned up as of 1c3e787..e328b44. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-16 09:02 | Marcello Stanisci | New Issue | |
| 2016-12-16 09:02 | Marcello Stanisci | Status | new => assigned |
| 2016-12-16 09:02 | Marcello Stanisci | Assigned To | => Christian Grothoff |
| 2016-12-16 09:04 | Marcello Stanisci | Description Updated | |
| 2017-03-02 07:04 | Christian Grothoff | Product Version | => git (master) |
| 2017-03-02 07:04 | Christian Grothoff | Target Version | => 0.5 |
| 2017-03-04 22:02 | Christian Grothoff | Severity | minor => feature |
| 2017-03-18 22:16 | Christian Grothoff | Relationship added | related to 0003887 |
| 2017-03-18 22:17 | Christian Grothoff | Note Added: 0011937 | |
| 2017-04-10 15:58 | Christian Grothoff | Relationship deleted | related to 0003887 |
| 2017-06-29 18:48 | Christian Grothoff | Note Added: 0012286 | |
| 2017-09-12 13:35 | Christian Grothoff | Note Added: 0012423 | |
| 2017-09-12 23:15 | Christian Grothoff | Note Added: 0012424 | |
| 2017-09-14 18:52 | Christian Grothoff | Note Added: 0012425 | |
| 2017-09-14 19:08 | Christian Grothoff | Note Added: 0012426 | |
| 2017-09-17 14:53 | Christian Grothoff | Note Added: 0012427 | |
| 2017-09-17 14:53 | Christian Grothoff | Status | assigned => informing |
| 2017-09-17 14:53 | Christian Grothoff | Resolution | open => fixed |
| 2017-09-17 14:53 | Christian Grothoff | Fixed in Version | => 0.4 |
| 2017-09-17 14:53 | Christian Grothoff | Target Version | 0.5 => 0.4 |
| 2017-10-18 13:42 | Christian Grothoff | Status | informing => closed |