-
Notifications
You must be signed in to change notification settings - Fork 104
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
messaging with phoenix? (keysend) #73
Comments
Thanks for the kind words @philbertw4! Let us know if that doesn't address the scenario you have in mind. |
Hi @t-bast, |
I really would like to see Phoenix with a chat like interface (or even with chat support too). Something like https://pine.pm/. So I could send payments to my contacts without need to request an invoice. |
Dear phoenix/acinq team,
First of all, I want to commend you on the work you've done with phoenix. By re-imagining the UX experience for what a bitcoin/lightning wallet can/should from a seamless, easy-to-use, perspective, I think you've moved the needle in a positive direction by quite a bit!
One of the reasons why I've found phoenix so much easier to use when it comes to onboarding less technically sophisticated users is how you guys essentially underwrite those initial channels. I realize there are security/privacy trade-offs (even if temporary) by having the wallet auto-peer with acinq such that instantaneous "channels" can be created. But given that the wallet remains non-custodial, and the usability (and risk of payment/routing failure) is vastly improved, this seems like a worthwhile tradeoff for now.
One thing I have wondered now is whether it might be possible to incorporate some sort of keysend functionality into phoenix. There seems to be a lot of promise in the various messaging-on-top-of-lightning projects (e.g. whatsat, juggernaut, etc), but for new people, especially those without full nodes already, to try those out it still requires a considerable time investment.
I wonder if, because of the clever way you handle the initial channels in phoenix, it might be possible for phoenix to essentially emulate keysend functionality for end users?
The text was updated successfully, but these errors were encountered: