Skip to content
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

feat: alby lite app #1056

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: alby lite app #1056

wants to merge 1 commit into from

Conversation

im-adithya
Copy link
Member

@im-adithya im-adithya commented Jan 31, 2025

⚠️ Proof of Concept - Not to be merged, yet.

Screenshot 2025-01-31 at 9 12 33 PM Screenshot 2025-01-31 at 9 13 04 PM

@im-adithya im-adithya requested review from bumi and rolznz January 31, 2025 15:44
@rolznz
Copy link
Contributor

rolznz commented Feb 1, 2025

Some thoughts + ones we talked about yesterday:

  • After our conversation about NIP-05 not being a good way to contact the user, I am wondering if this should be optional, as it's only really needed if you specifically want a albylite NIP-05 address.
  • This now "competes" with the Friends & Family app (which do we choose?). Would it make sense to move it there as an optional step after the account is created?
  • We have the issue that sub-wallets have spending permission. But we have not found a graceful way to handle this. Some of us think Alby Lite should not have spending access to wallets. It should have receive-only access.
  • From Rene: "Wasn't the main problem with Alby Lite that we didn't have a good answer for how the customer journey would look like for these people and it would make the existing product landscape even more complicated?" - we plan to have a call about this next week.
  • I like the idea about paying up-front especially if we find a way to do receive-only connections for alby lite.
  • From Moritz: There is another app we could make (based on Bumi's app) which is lightning addresses for receive-only isolated connections, where the lightning address itself contains the connection secret

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants