View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004475 | Taler | wallet (WebExtension) | public | 2016-04-27 14:14 | 2016-05-25 16:34 |
| Reporter | Florian Dold | Assigned To | Florian Dold | ||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004475: payment fails without clear error message if exchange "lost" keys and merchant doesn't accept the payment | ||||
| Description | If the exchange's denomination keys are lost (which should of course never happen) and the wallet tries to pay with one of those keys, we don't get any clear error message. The payment just fails with "backend error". Maybe the wallet should check before paying whether the denomination keys are still in /keys as a heuristic to generate better errors? The wallet should then offer the option to export proof (the exchange's signature on the keys it (wrongfully) no longer lists) | ||||
| Tags | No tags attached. | ||||
| parent of | 0004527 | closed | Florian Dold | merchant needs mechanism to inform wallet about failed payments |
|
|
When the merchant says that a denomination key is not found, it should send the /keys it got last from the exchange to the wallet. The wallet can then abort the payment or suspend the keys that the exchange did not give to the merchant. This all seems very messy, and we need to document it in some spec. |
|
|
At least suspending keys should be part of release 0.0. It's unacceptable that the wallet can enter a state where we can't do payments anymore because we have bad keys due to an exchange screw-up. This means that we'd have to tell people "please reset your wallet", that's unacceptable even for a 0.0 release. |
|
|
The merchant now returns the last /keys it got from the exchange. The wallet still needs to look at that and suspend keys appropriately. It also needs to "unsuspend" suspended keys if/once they're offered by the exchange again. |
|
|
Resolved (around 5dd21b1) in a somewhat hacky way. Keys are suspended, but right now this is somewhat transparent to the user. However it means that even when the exchange screws up, we're not in an unrecoverable state where we're forced to completely reset anymore. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-27 14:14 | Florian Dold | New Issue | |
| 2016-04-27 14:14 | Florian Dold | Status | new => assigned |
| 2016-04-27 14:14 | Florian Dold | Assigned To | => Florian Dold |
| 2016-04-27 16:37 | Florian Dold | Note Added: 0010572 | |
| 2016-05-05 15:25 | Christian Grothoff | Product Version | => 0.0 |
| 2016-05-05 15:25 | Christian Grothoff | Target Version | => 0.2 |
| 2016-05-09 08:45 | Florian Dold | Target Version | 0.2 => 0.0 |
| 2016-05-09 08:47 | Florian Dold | Note Added: 0010670 | |
| 2016-05-09 08:47 | Florian Dold | Priority | normal => high |
| 2016-05-24 02:36 | Florian Dold | Note Added: 0010725 | |
| 2016-05-24 16:44 | Florian Dold | Relationship added | parent of 0004527 |
| 2016-05-24 17:54 | Florian Dold | Note Added: 0010729 | |
| 2016-05-24 17:54 | Florian Dold | Status | assigned => resolved |
| 2016-05-24 17:54 | Florian Dold | Resolution | open => fixed |
| 2016-05-25 16:34 | Christian Grothoff | Status | resolved => closed |
| 2016-05-25 16:34 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2023-04-13 20:37 | Florian Dold | Category | wallet (WebExtensions) => wallet (WebExtension) |
