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

Ambiguity between multiple wallet views #119

Closed
pavlenex opened this issue Nov 28, 2024 · 3 comments
Closed

Ambiguity between multiple wallet views #119

pavlenex opened this issue Nov 28, 2024 · 3 comments
Labels
Milestone

Comments

@pavlenex
Copy link
Contributor

pavlenex commented Nov 28, 2024

I am sure we're aware of this , but would be good to discuss how we can clean this one up.

Let me try to recap all the views we have first:

  1. /funds which you access when you click on the Send on the dashboard.

Screenshot 2024-11-28 at 12 50 50

  1. settings/wallet/funds which you access from Settings> On-chain funds which has the functionality
    Screenshot 2024-11-28 at 13 07 04

  2. settings/wallet which is a duplicate of 4. Settings` > On-chain wallet

Screenshot 2024-11-28 at 13 18 09

  1. settings/walletwhich you access by Settings > On-chain funds clicking settings icon in the top right.

Screenshot 2024-11-28 at 13 18 09

I think we overcomplicated stuff here.

  1. is send
  2. is receive
  3. 3 and 4 are duplicates and we should remove onchain wallet setting and call this wallet settings

Just to bring things again into perspective:

Every wallet has 4 basic views:

  • /Wallet - transaction overview with balance send and receive buttons
  • Wallet/Send - sending
  • Wallet/Receive - receiving
  • Wallet/Settings - for wallet related settings

@dennisreimann I hope outlined this accurently, tbh it was quite tricky as I got lost in the navigation. Do you have any reasoning or ideas how we could tackle this cleanup? Perhaps there are some technical considerations I am missing out here, but I am sure a lot of this is caused by us not knowing specifically how we want to do this, and perhaps overthinking on the receive functionality.

@pavlenex
Copy link
Contributor Author

It seems @dennisreimann pushed some changes that make most of this issue obsolete now.

However, there are still two wallets for some reason:

  1. Dashboard > Send which is lightning + onchain (what we want) but it's dependent on wrong API points causing You need to allow non-admins to use hotwallets for their stores (in /server/policies) #117 Screenshot 2024-11-29 at 14 04 38

  2. Settings > On-chain wallet (which seems to be only on-chain wallet) and it works

Screenshot 2024-11-29 at 14 06 38

Ideal solution here is to have a single wallet, that unifies lightning and on-chain, but also works regardless of the server settings, so a combination of both views.

@dstrukt
Copy link
Member

dstrukt commented Dec 2, 2024

Agree, getting the foundation there was very helpful, but the views need to be unified and cleaned up now that they're working as intended!

@dstrukt
Copy link
Member

dstrukt commented Dec 2, 2024

Agree with @pavlenex and see a similar proposal:

  1. Wallet (either will be part of the Dashboard tab) or it's own tab
  • Includes the Unified Balance
  • Lists the latest transactions, possibly invoices
  • Send / Receive buttons
  1. Wallet/Send - Send view, accessible only through the Wallet

  2. Wallet/Receive - Receive view, accessible only through the Wallet, maybe we eventually add Lightning support here, but at the moment, Lightning receive is done through the Keypad

  3. Wallet/Settings - for Lightning and On-chain Wallet related Settings

No need for it to be more complicated.

@pavlenex pavlenex closed this as completed Dec 9, 2024
@github-project-automation github-project-automation bot moved this from Backlog 🪵 to Done ✅ in BTCPay App Roadmap 📱 Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants