View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011205 | Taler | wallet (all platforms) | public | 2026-03-06 12:31 | 2026-03-10 15:59 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | urgent | Severity | major | Reproducibility | have not tried |
| Status | feedback | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.5 | ||||
| Summary | 0011205: p2p transaction stuck on "KYC required" even though KYC is done at exchange | ||||
| Description | Student(s) had a fresh wallet (happened both with iOS and Android!), never used. P2P send them 3 CHF. Student did the KYC (SMS registration), but transaction still shows as KYC required in the wallet. Money did not arrive. On sending wallet, money is shown as paid out. | ||||
| Steps To Reproduce | Now, I believe I may have used an expiration time of 1h/1d and I believe the particular student(s) may not have done the KYC (SMS registration) immediately. So conceivably the student did it *after* the purse expiration time. Which doesn't exactly matter as the MERGE of the purse into the reserve already happened (hence the p2p transfer is 'final' on my end). But the withdraw failed, and maybe the wallet erroneously didn't re-try the withdraw after the purse expiration time? Note that other students that did the KYC immediately did receive the money, so this is most certainly timing-related. | ||||
| Tags | No tags attached. | ||||
|
|
Since the sender's wallet says that the transaction is complete, it means that the receiver *must* have done a successful merge. What's likely failing is creating the internal withdrawal transaction to withdraw from the reserve that the purse has been merged into. Difficult to diagnose without more details. Even if this was about outdated denominations, the wallet would eventually retry and succeed. |
|
|
I've not been able to reproduce this so far. What we need is either the error message (if there is one being displayed) or a DB export. (The diagnostics export doesn't contain enough info *yet*, but we should use this eventually instead of the full DB export) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-03-06 12:31 | Christian Grothoff | New Issue | |
| 2026-03-06 12:31 | Christian Grothoff | Status | new => assigned |
| 2026-03-06 12:31 | Christian Grothoff | Assigned To | => Florian Dold |
| 2026-03-10 00:22 | vecirex | Relationship added | related to 0011221 |
| 2026-03-10 00:22 | vecirex | Relationship deleted | related to 0011221 |
| 2026-03-10 14:33 | Florian Dold | Note Added: 0028078 | |
| 2026-03-10 14:35 | Florian Dold | Note Edited: 0028078 | |
| 2026-03-10 15:58 | Florian Dold | Note Added: 0028080 | |
| 2026-03-10 15:58 | Florian Dold | Assigned To | Florian Dold => Christian Grothoff |
| 2026-03-10 15:59 | Florian Dold | Status | assigned => feedback |
