View Issue Details

IDProjectCategoryView StatusLast Update
0003631Talerexchangepublic2015-03-29 12:23
ReporterChristian Grothoff Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityimmediateSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.0Fixed in Version0.0 
Summary0003631: design issue: denomination keys needed "forever"?
DescriptionWe 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).
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0003634 closedChristian Grothoff code needs to distiguish between active and old denomination keys 

Activities

Christian Grothoff

2015-03-22 14:50

manager   ~0009036

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.

Christian Grothoff

2015-03-28 13:26

manager   ~0009054

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.

Christian Grothoff

2015-03-28 13:27

manager   ~0009055

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.

Christian Grothoff

2015-03-28 17:40

manager   ~0009056

I've now checked the use(s) of all of the structs in taler_signatures.h; those should now be OK.

Issue History

Date ModifiedUsernameFieldChange
2015-01-28 23:52Christian GrothoffNew Issue
2015-01-28 23:52Christian GrothoffPrioritynormal => low
2015-01-28 23:52Christian GrothoffSeveritymajor => feature
2015-03-22 13:30Christian GrothoffRelationship addedrelated to 0003634
2015-03-22 14:50Christian GrothoffNote Added: 0009036
2015-03-22 16:20Christian GrothoffPrioritylow => high
2015-03-22 16:20Christian GrothoffStatusnew => implementing
2015-03-22 16:20Christian GrothoffTarget Version => 0.0
2015-03-22 16:20Christian GrothoffAssigned To => Christian Grothoff
2015-03-22 16:20Christian GrothoffStatusimplementing => assigned
2015-03-28 13:26Christian GrothoffNote Added: 0009054
2015-03-28 13:27Christian GrothoffNote Added: 0009055
2015-03-28 13:39Christian GrothoffPriorityhigh => immediate
2015-03-28 17:40Christian GrothoffNote Added: 0009056
2015-03-28 17:41Christian GrothoffStatusassigned => informing
2015-03-28 17:41Christian GrothoffFixed in Version => 0.0
2015-03-28 17:41Christian GrothoffResolutionopen => fixed
2015-03-29 12:23Christian GrothoffStatusinforming => closed
2016-02-18 14:43Christian GrothoffCategorymint => exchange