View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003819 | Taler | exchange | public | 2015-06-03 16:35 | 2024-01-12 14:05 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | major | 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 | 0003819: /deposit idempotency check is a bit lax | ||||
| Description | Right 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(). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-06-03 16:35 | Christian Grothoff | New Issue | |
| 2015-06-11 15:02 | Christian Grothoff | Target Version | => 0.0 |
| 2015-06-11 15:02 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2015-06-11 15:02 | Christian Grothoff | Status | new => assigned |
| 2015-06-12 11:53 | Christian Grothoff | Note Added: 0009274 | |
| 2015-06-12 11:53 | Christian Grothoff | Status | assigned => resolved |
| 2015-06-12 11:53 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2015-06-12 11:53 | Christian Grothoff | Resolution | open => fixed |
| 2015-06-15 14:17 | Christian Grothoff | Status | resolved => closed |
| 2016-02-18 15:44 | Christian Grothoff | Category | mint Postgres DB backend => exchange Postgres DB backend |
| 2024-01-12 14:05 | Christian Grothoff | Category | exchange Postgres DB backend => exchange |
