View Issue Details

IDProjectCategoryView StatusLast Update
0007252Talermerchant backendpublic2022-11-04 19:52
ReporterFlorian Dold Assigned Tooec Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.9Fixed in Version0.9 
Summary0007252: merchant doesn't accept payment for non-age-restricted order with age-restricted coins
DescriptionWhen 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 Reproducetaler-wallet-cli testing run-integrationtests age-restrictions
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

oec

2022-06-01 10:44

developer   ~0018910

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?

oec

2022-06-01 10:51

developer   ~0018911

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.

oec

2022-06-29 12:45

developer   ~0018949

Should be resolved with 72695e8e41bb75b44d3d09ad5316eb9d48ac25d7

Issue History

Date ModifiedUsernameFieldChange
2022-06-01 09:54Florian DoldNew Issue
2022-06-01 09:54Florian DoldStatusnew => assigned
2022-06-01 09:54Florian DoldAssigned To => oec
2022-06-01 10:44oecNote Added: 0018910
2022-06-01 10:51oecNote Added: 0018911
2022-06-29 12:45oecStatusassigned => informing
2022-06-29 12:45oecResolutionopen => fixed
2022-06-29 12:45oecNote Added: 0018949
2022-10-20 08:47Christian GrothoffFixed in Version => 0.9
2022-10-20 08:48Christian GrothoffTarget Version => 0.9
2022-11-04 19:52Christian GrothoffStatusinforming => closed
2025-03-22 13:09Christian GrothoffCategorymechant backend => merchant backend