View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011158 | Taler | exchange | public | 2026-02-25 12:35 | 2026-11-03 14:42 |
| Reporter | Antoine A | Assigned To | Resolution deadline | ||
| Implementer | Antoine A | Reviewer | Christian Grothoff | ||
| Release signed by | Antoine A | Deployed by | Florian Dold | ||
| Verifier | Antoine A | 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 | high | Severity | major | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Target Version | 1.7 | ||||
| Summary | 0011158: Clarify incoming wire transfer subject constraint | ||||
| Description | The current unspecified rule is that only a public reserve key can be used only once, whereas a KYC key can be reused and the same key can therefore be used once for the reserve and several times for KYC. We need to specify this formally somewhere (in the wire gateway API?) and ensure that the exchange and wire gateway implementations behave consistently. | ||||
| Tags | discussion-needed | ||||
| Ah, we only allow ONE KYC AUTH transfer per unique subject AND origin account. Which makes sense, as more than one is clearly redundant. ;-). Now, we could relax that constraint, or libeufin can just 'hide' those duplicate transactions from the exchange. Is the latter hard to do? | |
| So a different account can reuse the key ? I would prefer to enforce the rule of one key can only be used once, this make everything simpler and I guess it's what we currently have in the database as it never crashed before | |
| We could allow the same key to be used once for KYC and once for reserve as it can be stored in different DB tables, but most wire gateway would be more restrictive and clients should not try reuse them | |
| With the new registration endpoint, wallet can check for reuse before making a transfer. This means bounces should never happen under normal use after this change | |
| Yes, another account can reuse the key. In fact MUST: you can have a single merchant instance (=key) with multiple bank accounts. So for that scenario, the merchant would have to use the same key from multiple accounts. | |
| As for new endpoint: you still must handle the case where you do get duplicate incoming wire transfers -- say from clients that don't use the new endpoint. | |
| Ok, let's keep the same logic then | |
| Ok, so assign bug to you or consider resolved or what? | |
| How hard would it be for the exchange to tolerate many KYC per account ? Doing so at libeufin level is a bit of a pain | |
| What do you mean? Multiple KYC auth wire inputs are OK, but we have only one KYC *record set* per account and would only do the KYC process once. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-25 12:35 | Antoine A | New Issue | |
| 2026-02-25 12:35 | Antoine A | Status | new => assigned |
| 2026-02-25 12:35 | Antoine A | Assigned To | => Christian Grothoff |
| 2026-02-25 12:40 | Christian Grothoff | Note Added: 0027884 | |
| 2026-02-25 12:44 | Antoine A | Note Added: 0027885 | |
| 2026-02-25 12:48 | Antoine A | Note Added: 0027886 | |
| 2026-02-25 12:49 | Antoine A | Note Added: 0027887 | |
| 2026-02-25 13:15 | Christian Grothoff | Note Added: 0027891 | |
| 2026-02-25 13:16 | Christian Grothoff | Tag Attached: discussion-needed | |
| 2026-02-25 13:17 | Christian Grothoff | Note Added: 0027892 | |
| 2026-02-25 13:20 | Antoine A | Note Added: 0027894 | |
| 2026-02-25 14:28 | Christian Grothoff | Note Added: 0027895 | |
| 2026-02-25 14:35 | Christian Grothoff | Assigned To | Christian Grothoff => Antoine A |
| 2026-02-25 14:35 | Christian Grothoff | Status | assigned => feedback |
| 2026-02-25 14:36 | Antoine A | Note Added: 0027896 | |
| 2026-08-29 19:44 | Florian Dold | Target Version | => 1.7 |
| 2026-11-03 14:41 | Christian Grothoff | Note Added: 0030215 | |
| 2026-11-03 14:42 | Christian Grothoff | Assigned To | Antoine A => |
| 2026-11-03 14:42 | Christian Grothoff | Implementer | => Antoine A |
| 2026-11-03 14:42 | Christian Grothoff | Reviewer | => Christian Grothoff |
| 2026-11-03 14:42 | Christian Grothoff | Release signed by | => Antoine A |
| 2026-11-03 14:42 | Christian Grothoff | Deployed by | => Florian Dold |
| 2026-11-03 14:42 | Christian Grothoff | Verifier | => Antoine A |
| 2026-11-03 14:42 | Christian Grothoff | Status | feedback => implementing |