11.68. DD 68: Token Feature Roadmap#

Status: incomplete draft (2025-07-31)

11.68.1. Summary#

This design document documents the roadmap for token types supported by Taler.

11.68.2. Motivation#

11.68.3. Plan for Wallet#

Types of tokens:

donations tokens (hard deadline: End of November)
- onboarding (1st donation)
  - ask for tax payer id, add taxOfficeBaseUrl (only one per wallet)
  - can be changed, but new donations will have a different tax payer ID
  - store date with tax payer ID for merge
- reporting: per year, one QR code per: (taxPayerId, walletSalt, year)
  - meta data per QR code: taxPayerId, walletSalt, year, taxOfficeBaseUrl
  - out of scope: generate PDF
  - listing: just show sum (per tax payer ID and year and salt), not individual tokens
- listing: there is separate listing for tokens
- delete: out of scope for now / future work
subscription
- listing
  - Expired tokens are deleted automatically after grace period (30 days).
  - Consider not deleting the last token of a particular slug. Maybe in the future, subscription tokens will have a link to re-purchase them.
  - No counter
  - Show expiration date
- delete (with big fat warning)
discount tokens
- listing (type and number, description) * group by expiration date (if it exists)
- delete
asset tokens (deadlines: end of March)
- listing (with number, no fractions possible, no expiration)
- background task: poll for share action, automatically execute the share action
  - share action dividend: not supported for now
  - share action voting: multiple in parallel possible, maybe show vote weight, have expiration date
  - votes are grouped under the respective asset tokens
- voting action
  - normally grouped under asset token (“history” for corporate actions)
  - in notificiation state: vote directly or dismiss
  - eventually, result is fetched and shown
- divident (initially out of scope)
  - normally grouped under asset token (“history” for corporate actions)
  - in notificiation state: dismiss, auto-dismiss after some time

11.68.4. Plan for Merchant Backend#

TBD.

11.68.5. Plan for Donau#

Service exists
Needs to packaged

11.68.6. Test Plan#

Subscription/discount: blog.demo.taler.net
Donations: donations.demo.taler.net
- Receipt validation: TBD
Asset tokenization: TBD / will be deployed on demo via merchant

11.68.7. Definition of Done#

Donau deployed in sandcastle
donations in demo must use donau / contracttermsv1
use separate app (prototype exists?) for verification of receipts

11.68.8. Discussion / Q&A#

(This should be filled in with results from discussions on mailing lists / personal communication.)

DD 68: Token Feature Roadmap

Contents