You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No way to switch between “Savings” and “Spending” after scanning a unified QR code
Describe the solution
Balance Toggle Functionality: It would be nice to allow the sender to switch between “Savings” and “Spending” after scanning a unified QR code (see mockup video)
Fixed States for Toggle:
• For On-chain-only QR codes, the toggle will be set to a fixed “Savings” state (see mockup video).
• For Lightning-only invoices, the toggle will be set to a fixed “Spending” state.
pwltr
changed the title
[Feature]: Send to Contact (unified QR)
[Feature]: Add ability to switch between sending from savings & spending (unified QR)
Sep 16, 2024
Tested on v1.0.7 and v1.0.8
Toggles show correctly and work well. Static labels show when they should for onchain address and LN invoiced.
It would be nice to also show the label for lnurl, rraised #2413
Tapping the available balance to apply max value shows an orange "Reserve Balance" toast message that reads "The maximum spendable amount is a bit lower due to a required reserve balance."
Describe the problem
No way to switch between “Savings” and “Spending” after scanning a unified QR code
Describe the solution
Balance Toggle Functionality: It would be nice to allow the sender to switch between “Savings” and “Spending” after scanning a unified QR code (see mockup video)
Fixed States for Toggle:
• For On-chain-only QR codes, the toggle will be set to a fixed “Savings” state (see mockup video).
• For Lightning-only invoices, the toggle will be set to a fixed “Spending” state.
Max amount: Added max amount modal with short explanation for end user for when ‘max’ amount is tapped in spending balance send flow. https://synonymworkspace.slack.com/archives/C01H106JRQB/p1712855096363569?thread_ts=1712850323.807499&cid=C01H106JRQB
Additional context
No response
The text was updated successfully, but these errors were encountered: