-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a /redeem route #901
Comments
not sure where/how it should be handled but wondering about cases where the amount of the cashu token pasted is very low. Should we show a warning or something instead of a redeem button if the amount is too low? |
yes, at least for fedimint the oob's have fixed amounts
I don't have any specific thoughts about it, and I agree that unifying it would be better. The only thing is that currently, OOB would only work with copy/paste and not through QR, could that lead to bad UX somehow ? 🤔 |
@elnosh what would too low mean, it's all burned to fees? |
maybe something below 5 sats. That could end up going most of it in fees. |
I just noticed that current LNUrlW implementation does not give access to the invoice that is processed. Showing a QR (that is never used) does not make much sense during processing. It will need access to the tx to show the exact received amt in the success screen later though. |
You can just offer to trust the origin mint and do a swap instead of melting the cashu to LN. Then no fees. |
We have three (THREE!) new ways to get money into mutiny in PRs currently:
#885
#891
#837
All three work on the premise of you pasting in something, and then you see some sort of preview, and then you click a button and get the money. (Potentially gifting can work like this as well, although rn it has its own path / ux)
LnurlW is a bit different because it can, optionally, have an editable receive amount, afaik cashu and fedi oob will always be fixed amounts.
I plan on building the
/redeem
route to unify these, just wanted to make this a discussion issue of any thoughts / gotchas I might need to have in mind when trying to unify the UX here.@oleonardolima @elnosh @tompro any thoughts / special considerations I should be aware of?
The text was updated successfully, but these errors were encountered: