If you receive salary on-chain, you probably want to withdraw to cold storage once you hit a threshold amount. (similar to how auto-swaps work right now)

After several successful payouts to my first BOLT12 offer, my Alby Hub had an issue and I missed a payment due to the outage. However, the next payment attempt received an error from the sender. I then realized there was no way to check all current BOLT12 offer Invoices, including related payments per invoice..

It would be nice to be able to choose which Lightning implementation to use. Core Lightning is also very stable and offers cool features like BOLT12, so please consider adding support for it.

Implement a persistent toggle for the "Stats for Nerds" option on the home screen. Ideally integrate the stats display across the top of the screen when toggled on to eliminate the need for scrolling on smaller screens.

Expose LDK Lightning Node onion address for Tor Connection to fund a Fedimint

When using embedded LDK Lightning Node in Alby Hub, add the ability to backup the Node's private keys like you can with LND or Core Lightning

Please add the Amont field to a Lightning Offer while still defaulting to 'Any'

In the backups page of the node settings, the word "lose" is spelled as "loose"

and then we can maybe talk about retrieving my balance that has disappeared!

When someone give us their lightning address, I realized it is likely we will send sats to that same person again. Let's store the lightning addresses that we have sent money to by default in a contact list. With option to remove them in case we need to. But it would be nice to have a recurrent sender's contact list. This adds another social layer to the app. Having our friends on the list makes us feel more at home when we see them as contacts of our wallet.

I created a lightning address for a sub-wallet. I would like to transfer it to full Alby Account. For that I need to delete it first.

Many jurisdiction impose tax rules based on capital gains. The tax is based on the difference between the acquisition and sale price.
Tracking the acquisition and sale price in Alby Hub would be very useful.
Or a some guidance to create exports and importing it into a spread sheet.

We should be able to toggle off our total balance

You can set a fee when sending via on-chain or withdrawing on-chain funds, but if there is a fee spike and your transaction is time-critical you should be able to have a way to bump the transaction.

I prefer not to switch between apps and wallets all the time: I’d like to manage everything from my Alby Hub & Alby Go.

For on-chain funds going to an offline wallet, I’d like the option to add an xpub for view-only balances and address generation into the Hub. That way I can create new on-chain addresses without having the use the online Hub’s seed. 🔒

This should be something very different than the current onchain balance, it should be a piggy bank section or "your safe offline storage" section, hidden somewhere to avoid confusion and let only advanced users use this.

This does add complexity, but it improves usability and security for advanced users. It shouldn’t be easily accesible or enabled by default, and the flow should be clearly documented, what an xpub is, why you’d use it, so non-advanced users can follow along. 📖🧠.

This safe offline storage can also work for having referal links to exchanges that let you buy bitcoin directly to your onchain offline wallet for exactly safe storage. So it has the potential to help users that are already doing this, but also to assists new users interested on safe offline storage to be able to just view everything from the hub and not having to learn anything else somewhere else. There is also reveneu oportunity on very small comissions for linking bitcoin sellers with those users.

Thanks for considering it.

Lets users instantly check for Address Swaps

Could be nice to see how payments went (through which channels) and where they incurred how much fees and how much was the fee in total.

As a user I might have bought several channels. With the current invoice (Alby - invoice: ALB-5498-xxxx-001 (Lightning Channel)), I don't know for which channel exactly I was billed.

When pressing the red close button, a helpful warning appears that the app needs to keep running for Lightning payments to work.

This is important and good.

Current behavior:
The app can only be minimized to keep running in the background. When minimized, a second window appears on the far right of the Mac Dock (as an additional Alby Hub window). This behavior is disruptive.

My wish is to truly close the app via the red close button. At the same time, I want Swift Quit (Application to handle windows in iOS) to prevent the app from fully terminating, allowing it to continue running in the background—without the annoying additional Dock window.

Problem:
The warning about quitting always shows and cannot be disabled. This interrupts and disturbs the workflow because I actually want to close the app, but effectively it can only be minimized, causing an extra window in the Dock which stays there for ever.

Suggestion:
Please add an option in the Alby Hub settings to disable the quit warning.

This way, when I close the app using the red button, it truly closes, and Swift Quit ensures it continues running in the background—without an extra Dock window always open.

This would enable a clean iOS workflow that allows background operation without disruptive Dock additional App windows.

Would be nice to have an option to have a log in screen with plain albyhub branding rather than the shadowy figures with the quotes about bitcoin.

It has a very "tin foil hat" feel to it and I think it would put a lot of people off Albyhub. I Certainly cringe pretty hard every time I have to unlock my wallet.

A watchtower service, part of the Pro plan to monitor node channels if offline

Since recommended channel sizes at usually 1M sats or more, and multiple channels are needed. Users are expected to be holding non-trivial balances on Alby Hub.

Also the Hub account controls user's nodes.

Thus, Alby Hub should allow users to add 2FA through authenticator apps as a additional security measure.

Channels close because some have a fixed duration or because of low activity. A warning before the channel closes would be useful. Especially if there is a chance to keep it open if payment activity increases.

I came across this Github issue: https://github.com/getAlby/hub/issues/1504 and would like to add this as a feature request here.

The Problem:
Receiving on Lightning is not very private, since all invoices by default include your nodeid. It has been common practice in all LN node implementations (LND, CLN, eclair) to assign a fixed nodeId, which makes it easy to fingerprint you and is bad for privacy.

However, this is not technically necessary. If you are not a routing node (i.e. only have private channel), there is absolutely no need to have a fixed nodeid - it can be randomized each time you generate an invoice (you just have to include route hints in the invoice then).

The Solution:
[Technical details in the linked Github Issue]

tl;dr : generate a random nodeid for each invoice, and add a routing hint - for AlbyHubs using the embedded LDK node with private channels only.

Fyi, This was done already years ago by Simple Bitcoin Wallet and is maintained to this day in its fork. It's a proven technique.

Implementation:
Could be done via optional toggle, experimental settings for the beginning. Once stable, rolled out for GA.

Can we get this in Alby Hub??
This would be a massive upgrade for Lightning privacy!! 🙏

Create a UI that only shows all sending and receiving failures with some information to why so that they can be addressed. Same for any errors when creating invoices for payers. The goal is to get those to zero.