View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003631 | Taler | exchange | public | 2015-01-29 00:52 | 2015-03-29 14:23 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | immediate | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0003631: design issue: denomination keys needed "forever"? | ||||
| Description | We cannot check transaction histories "properly" without knowing the associated denomination key VALUES. Right now, we often "only" store the public key of the denomination key, which is good and OK as storing the corresponding value would be redundant (and then we'd still not have hard proof, as the hard proof comes from the signatures on the value of the denomination key(s)). However, if we want to check the balance of a reserve (and thus must look at its full transaction history), we need all denomination keys in the history (and their respective valuations). This includes denomination keys that are not used by the mint for a long time, as reserves don't really expire. Is this an issue? Right now, the only good solution that comes to my mind is to simply never get rid of denomination keys (they are not big and stored in a hash table, so likely no huge problem for a LONG time). | ||||
| Tags | No tags attached. | ||||
| related to | 0003634 | closed | Christian Grothoff | code needs to distiguish between active and old denomination keys |
|
|
Changed the *structs* so that the signed messages are to include the transaction value AND fee instead of (just) the denomination key. That should address this issue; however, the rest of the code still needs to be adjusted accordingly. |
|
|
Improved structs a bit more, so now all (but the offline master key) key materials make it clear when they expire for good. The validity of the offline master key should probably be tied to the auditor, so that's still outside of our immediate concern. |
|
|
This bug remains open as we need to update the code to actually consistently use all of the fields we now have in the structs. |
|
|
I've now checked the use(s) of all of the structs in taler_signatures.h; those should now be OK. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-01-29 00:52 | Christian Grothoff | New Issue | |
| 2015-01-29 00:52 | Christian Grothoff | Priority | normal => low |
| 2015-01-29 00:52 | Christian Grothoff | Severity | major => feature |
| 2015-03-22 14:30 | Christian Grothoff | Relationship added | related to 0003634 |
| 2015-03-22 15:50 | Christian Grothoff | Note Added: 0009036 | |
| 2015-03-22 17:20 | Christian Grothoff | Priority | low => high |
| 2015-03-22 17:20 | Christian Grothoff | Status | new => confirmed |
| 2015-03-22 17:20 | Christian Grothoff | Target Version | => 0.0 |
| 2015-03-22 17:20 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2015-03-22 17:20 | Christian Grothoff | Status | confirmed => assigned |
| 2015-03-28 14:26 | Christian Grothoff | Note Added: 0009054 | |
| 2015-03-28 14:27 | Christian Grothoff | Note Added: 0009055 | |
| 2015-03-28 14:39 | Christian Grothoff | Priority | high => immediate |
| 2015-03-28 18:40 | Christian Grothoff | Note Added: 0009056 | |
| 2015-03-28 18:41 | Christian Grothoff | Status | assigned => resolved |
| 2015-03-28 18:41 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2015-03-28 18:41 | Christian Grothoff | Resolution | open => fixed |
| 2015-03-29 14:23 | Christian Grothoff | Status | resolved => closed |
| 2016-02-18 15:43 | Christian Grothoff | Category | mint => exchange |
