commit 9bf6ea3483c8e7426141fe1f0d979e70e4e043b3
parent 792f2001051ef66384d7ffd14ddb9c77bfeabcd5
Author: bohdan-potuzhnyi <bohdan.potuzhnyi@gmail.com>
Date: Sun, 6 Sep 2026 17:44:24 +0200
dd98 in development update
Diffstat:
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/core/merchant/post-fountain-withdraw.rst b/core/merchant/post-fountain-withdraw.rst
@@ -89,7 +89,8 @@
h_issue: HashCode;
// Blind signatures, in the same order as the ``envelopes``
- // of the request entry, as in the pay protocol
- // (`TokenIssueBlindSig`).
- blind_sigs: TokenIssueBlindSig[];
+ // of the request entry. Uses the same format as token_sigs
+ // in the order payment response: each entry wraps a
+ // TokenIssueBlindSig in a blind_sig field.
+ token_sigs: SignedTokenEnvelope[];
}
diff --git a/design-documents/098-token-fountains.rst b/design-documents/098-token-fountains.rst
@@ -8,7 +8,7 @@ DD 98: Token Fountains for Promotions
:DD shepherd: TBD
:Historical contributors: Bohdan Potuzhnyi
:First published: 2026-07-23
-:Last substantive change: 2026-07-24
+:Last substantive change: 2026-09-06
:Normative references: ``core/api-merchant.rst`` (upcoming token-fountain API)
Summary
@@ -228,6 +228,9 @@ issue public keys needed to prepare blinded envelopes.
envelopes. The request is grouped by token family and issue-key slot so that
the backend can enforce each grant's limits.
+Each grant result returns ``token_sigs`` using the same
+:ts:type:`SignedTokenEnvelope` format as the order payment response.
+
Deletion invalidates future requests using the credential. It does not
invalidate tokens that the wallet already withdrew.