View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007252 | Taler | merchant backend | public | 2022-06-01 11:54 | 2022-11-04 20:52 |
Reporter | Florian Dold | Assigned To | oec | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 0.9 | Fixed in Version | 0.9 | ||
Summary | 0007252: merchant doesn't accept payment for non-age-restricted order with age-restricted coins | ||||
Description | When paying for a non-age-restricted order with age-restricted coins, the wallet creates a deposit permission with the fields dp.minimum_age_sig = undefined; // because we don't need to attest age dp.age_commitment = ac; // because the merchant needs to compute h_age_commitment to check deposit permission However, the merchant doesn't like that combination: { "code": 26, "hint": "A parameter in the request was malformed.", "detail": "inconsistency: 'mininum_age_sig' vs. 'age_commitment'" } The merchant ought to either accept this combination or require explicit passing of h_age_commitment in the deposit request if the coin is age restricted, no matter whether the order is age restricted or not. | ||||
Steps To Reproduce | taler-wallet-cli testing run-integrationtests age-restrictions | ||||
Tags | No tags attached. | ||||
|
Good catch. We _could_ reuse the field 'age_commitment' for the _hash_ of the age commitment in the case that 'minimum_age_sig' is undefined and minimum age wasn't required. What do you think? |
|
Well, clearer yet, let's have an optional field 'h_age_commitment' that must be set by the wallet in case of minimum age wasn't required and the coin had age commitment set. |
|
Should be resolved with 72695e8e41bb75b44d3d09ad5316eb9d48ac25d7 |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-06-01 11:54 | Florian Dold | New Issue | |
2022-06-01 11:54 | Florian Dold | Status | new => assigned |
2022-06-01 11:54 | Florian Dold | Assigned To | => oec |
2022-06-01 12:44 | oec | Note Added: 0018910 | |
2022-06-01 12:51 | oec | Note Added: 0018911 | |
2022-06-29 14:45 | oec | Status | assigned => resolved |
2022-06-29 14:45 | oec | Resolution | open => fixed |
2022-06-29 14:45 | oec | Note Added: 0018949 | |
2022-10-20 10:47 | Christian Grothoff | Fixed in Version | => 0.9 |
2022-10-20 10:48 | Christian Grothoff | Target Version | => 0.9 |
2022-11-04 20:52 | Christian Grothoff | Status | resolved => closed |
2025-03-22 14:09 | Christian Grothoff | Category | mechant backend => merchant backend |