View Issue Details

IDProjectCategoryView StatusLast Update
0003819Talerexchangepublic2024-01-12 13:05
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
PrioritynormalSeveritymajorReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.0Fixed in Version0.0 
Summary0003819: /deposit idempotency check is a bit lax
DescriptionRight now, if a merchant uses the same transaction ID for two deposits involving the same coin (but possibly different amounts, sepa details, contracts, etc.), the mint will ignore the 2nd one silently as a 'duplicate', without ever reporting an error.

The logic is in #postgres_have_deposit().
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2015-06-12 09:53

manager   ~0009274

Implemented in ec56e47..cf8d671

Issue History

Date ModifiedUsernameFieldChange
2015-06-03 14:35Christian GrothoffNew Issue
2015-06-11 13:02Christian GrothoffTarget Version => 0.0
2015-06-11 13:02Christian GrothoffAssigned To => Christian Grothoff
2015-06-11 13:02Christian GrothoffStatusnew => assigned
2015-06-12 09:53Christian GrothoffNote Added: 0009274
2015-06-12 09:53Christian GrothoffStatusassigned => informing
2015-06-12 09:53Christian GrothoffFixed in Version => 0.0
2015-06-12 09:53Christian GrothoffResolutionopen => fixed
2015-06-15 12:17Christian GrothoffStatusinforming => closed
2016-02-18 14:44Christian GrothoffCategorymint Postgres DB backend => exchange Postgres DB backend
2024-01-12 13:05Christian GrothoffCategoryexchange Postgres DB backend => exchange