View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008011 | Taler | specification | public | 2023-12-16 04:30 | 2024-03-07 19:47 |
| Reporter | sebasjm | Assigned To | Christian Grothoff | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | 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 | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.4 | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0008011: return list of trusted exchange in /config | ||||
| Description | currently after finish instance setup the merchant needs to setup the bank account. right now merch backoffice SPA allows to configure any type of bank account but this should be filtered by the list of accepted wire target from trusted exchange and this information should be exposed by merchant /config | ||||
| Tags | No tags attached. | ||||
| the create reserve form requires the user to type the exchange base url. we can use the list of trusted exchange exposed by /config to preset the list with the most common exchange where merchants are going to create reserve for reward | |
| Well, returning the list of configured exchange URLs is trivial, but giving you the associated wire methods is a completely different story, as that can (1) change, (2) be unavailable if an exchange is down or we simply did not yet get a response. /config is IMO supposed to be *static* and instantly available, not something that changes dynamically (modulo restarts of the service after uncommon configuration changes). So I do not exactly like the idea of returning the wire methods here. I'm also not sure that it is even a good idea to not allow the user to configure a wire account merely because no exchange (currently!) supports this wire method, again for the same reason: it might just be that the exchange is temporarily unavailable! | |
| exchange URLs, master pubs and currencies are returned starting with protocol v6. Note that the wire methods are NOT returned, and I do not think they should be. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-16 04:30 | sebasjm | New Issue | |
| 2023-12-16 04:30 | sebasjm | Status | new => assigned |
| 2023-12-16 04:30 | sebasjm | Assigned To | => Christian Grothoff |
| 2023-12-16 04:41 | sebasjm | Note Added: 0020766 | |
| 2023-12-17 00:24 | Christian Grothoff | Severity | minor => feature |
| 2023-12-17 00:27 | Christian Grothoff | Note Added: 0020771 | |
| 2023-12-17 14:17 | Christian Grothoff | Status | assigned => informing |
| 2023-12-17 14:17 | Christian Grothoff | Resolution | open => fixed |
| 2023-12-17 14:17 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2023-12-17 14:17 | Christian Grothoff | Note Added: 0020772 | |
| 2023-12-22 13:39 | Christian Grothoff | Target Version | => 0.9.4 |
| 2024-01-12 13:02 | Christian Grothoff | Category | merchant backend API (HTTP specification) => specification |
| 2024-03-07 19:47 | Christian Grothoff | Status | informing => closed |