| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009958 | Taler | specification | public | 2025-05-14 17:08 | 2025-12-07 09:53 |
| Reporter | avalos | Assigned To | vlada.svirsh | 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 | text | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0009958: write a design document on how to render insufficient balance hints | ||||
| Description | Currently, wallet-core reports a hint on different causes of insufficient balance: export enum InsufficientBalanceHint { MerchantAcceptInsufficient = "merchant-accept-insufficient", MerchantDepositInsufficient = "merchant-deposit-insufficient", AgeRestricted = "age-restricted", WalletBalanceMaterialInsufficient = "wallet-balance-material-insufficient", WalletBalanceAvailableInsufficient = "wallet-balance-available-insufficient", ExchangeMissingGlobalFees = "exchange-missing-global-fees", FeesNotCovered = "fees-not-covered", } This is, however, up to the UI to render correctly, which is currently not the case, as seen in the attached screenshot, where users are still confused as to why the balance is insufficient. Thus, a design document should be drafted, in which the strings and visual cues are documented for each case of insufficient balance, so that the message is clearer to the end user. | ||||
| Tags | debt | ||||
- Anonymous